I’m struggling to migrate sdk v2 code to sdk 3.0
I have a query that I run to fetch an item using some secondary key (unique key). This was done before with the sdk 2 implementation. latency were usually below 40ms. The query is simple and works on an index and accept this id as a parameter. The queries rate is about 1-3 per second. the process also involves kv operations, such as get entities and counter get/increment.
When running the same functionality with sdk 3 (3.0.4) I get after about 1 hour of running a latency spikes of about 1-3 seconds. there’s no rise in the rps, it justs starts to slow down. I activated metrics on this request and saw that server execution time is 10ms, even for these long requests. other services in our cluster which work with sdk 2 don’t experience any latency.
again, this always occur after many many successful requests. but then when latency starts, I get a lot of requests like that.
a note about the migration process: the original code with sdk 2.0 works with the dsl library you removed from sdk 3. I’m not sure it should have any effect.
I tried to play with maxHttpConnection but it didn’t seem to help in any way.
Do you have some advice on how solve it?