What are the recommended routing configs (more specifically, the

segmentPrunerTypes

config) for an upsert table? The partition key (say

pk

) in my upsert table is the hashed value of two concatenated id fields (lets say

A

and

B

), and the most common pattern of queries against that table is filtering on column

A

instead of the

pk

.

A is one of the columns in PK?

Yes

Yea for partitioner pruner the partitioning has to match. There’s a column value pruner that you can use. However, what’s the read latency and qps you require? Not setting any pruner will also be quite fast

For now, our QPS is pretty low, at peak is just 10~20, but in the near future it will be thousands or even much more. However, even with current low QPS, sometimes we the latency can go up to 1s, which is not acceptable. We want the latency to be under 100ms.

Would be good to understand why the latency goes up, where’s the bottleneck and will pruning help

Yeah we tried giving resources and it looks like does help. But want to see if there are any other things we can optimize.