request are starved during concurrent searches

[a-bawane]

I conducted load testing with JMeter at a rate of 100 queries per second (QPS) with a 10-minute hold time. During this test, I noticed that some requests experienced delays and were only served towards the end of the hold time. This delay was consistent for both text and SQL search queries. For reference, I have attached the Aggregate Report.

In the report, the minimum response time was 61 ms, the maximum response time reached 675398 ms, and the 90th percentile response time was 1424 ms. Considering that there were only two unique requests, these response times appear to be on the higher side.

I'm looking for suggestions on how to scale the system to handle a higher QPS rate. Any advice or recommendations would be greatly appreciated.

[davidmezzetti]

I don't have any immediate suggestions. I would have to debug the use case and see what bottlenecks are there. I'll keep this open and follow up when I have time to take a detailed look.