Thanks for the bump.

There's not really a good way to do this right now with NDK. I think your best bet is probably to do some sort of fanout (ideally with multiple processes).

Mostly I've gotten around this in the past by doing it the slow way but storing users in an in-browser cache (using something like Dexie) so they're fast after that.