The embedded lookup tables are computed Query side as they are specific to
the (encrypted) query vectors. The 'embedded' part is key here - if you
compute them in the Responder, then you have to repeat that computation
each time you would like to run the query instead of just pulling the
On 29/09/16 11:29, Ellison Anne Williams wrote:
> In general, I am in favor of an abstract class.
>
> However, note that in the distributed case, the 'table' is generated in a
> distributed fashion and then used as such too ('split' and distributed).
>
> FWIW - In preliminary testing, the lookup
In general, I am in favor of an abstract class.
However, note that in the distributed case, the 'table' is generated in a
distributed fashion and then used as such too ('split' and distributed).
FWIW - In preliminary testing, the lookup tables ended up not performing
any better at scale than the
