Open
Description
We are looking for a way to shard our data and process queries in parallel across shards. Our SQL is unpredictable and difficult to optimize (it comes from a query generator). ActorDB seems like an interesting option. I can't tell from the documentation whether or how it handles the situation where we have the data sharded into many more shards than there are processors/threads on the server. Is there a queuing mechanism? For example, with 16 cores, is there a way to iterate over all of the shards in groups of 16 at at time? Apologies if I am not understanding how it works and this should be obvious. Thanks in advance.
Metadata
Metadata
Assignees
Labels
No labels