Running with -q hangs

[black-snow]

When I run oha with -q (and -w?) is just hangs at some point. It doesn't drain any CPU than and seems just dead-locked.

Example: oha -q 5 -z 30s -m POST -t 30s -d "$body" -T 'application/json' -w 'http://localhost:8000/score'

Sometimes it hangs after 4 seconds, somtimes after 22.

[devnev]

Same for me, with oha -z 10s -q 30 -t 5s <url>, both with and without --no-tui, it hangs after a few seconds, and I have to pkill oha from a different terminal

[hatoo]

Thank you for your reports.

Could you tell me a OS and oha's version?

[devnev]

oha 1.4.7, installed with brew, MacOS Sonoma 14.5, Intel x64.

I'm actually finding that if I replace -z 10s with -n 300 it works. There's some weirdness but I'm not sure if that is from oha or the service I'm testing.

[black-snow]

oha 1.4.7

macOS (14 and 15, M3 chip) as well as various Linuxes (amd64)

[hatoo]

I can't reproduce it in both MacOS15 x64 and Ubuntu x64.

Could you tell me about the server side? If codes aren't available, please tell me the language and framework versions.

Is the -t option necessary to reproduce this issue?

[black-snow]

Sadly, I can't test right now. The server is a Python app (3.12, fastapi + uvicorn both latest).

[nekevss]

I'm having the same issue with oha version 1.4.7 on Pop!_OS 22.04 where it hangs when provided -z 2m -q 1 (optionally with -w). I have found that adding --latency-correction does stop oha from hanging, but that's probably due to avoiding client::work_until_with_qps.

[black-snow]

Another exec that hangs: oha -q 30 -z 10s -m POST -t 30s -w -d "$body" -T 'application/json' 'http://localhost:8000/get_score'

Will try with -n instead of -z.

---

No hang so far. But other interesting things happen. I guess it's due to timeouts? I set a qps of 10 and my endpoint is rather slow. oha starts off fine but then drops rps to zero, nothing happens for a bit, rps goes up a bit only to drop down to zero again, then after some time the progress bar continues to fill up but "Slowest" says "-inf".

Perhaps I don't quite understand what "Requests" in the upper left corner should tell me - when I set -q10 I'd expect it to pretty much always read 100 - it says "stats for the last 10s". Yet, when I run against the slow endpoint it sits somewhere between 0 and 4, then at some point the progress bar on the top progresses very quickly (but requests stats remains low).

[hatoo]

I think it's fixed in #613
Feel free to reopen this issue
Thank you!

[black-snow]

Nice! Looking forward to the next release then.