Post

It runs queries against a database. I suspected the connection pool, but the same behavior is exposed when just returning some dummy data from the service itself. Starting to wonder whether it's an artifact of the load generator (oha) and/or running this on macOS. Will try on a Linux box.

Ha, yeah, turns out it was on the load gen side indeed. It was running out of connections. Using HTTP2 mitigates it (via pipelining), which I got reminded of reading the docs of... Hyperfoil ;) Is the project alive? Saw the last post is from a few years back.

1 repost1 like

Yeah, I was running into connection limits, which you can sidestep by using keep-alive or HTTP2 (if that fits the spec for your test). But I'm seeing some random noise with oha, which make tail latencies not very trustworthy.

Load gen as bottle eck, nice classic! Wasn't this what Gatling was originally meant to solve (vs jmeter which didn't do that well)?