Re^2: Benchmarking Perl's Net::Async::FastCGI app consistently return LOTS of "Non-2xx responses"

I already tried reducing both the number of total requests to 40, and concurrent requests to 20; and it still returns 24 "Bad Gateway"s. Since a concurrent requests level of 20 is really child-play, there's something very funky going on here. Using TCP port number instead of Unix socket makes it even worse. I literally use the helloworld example verbatum (except for the Unix socket tweak) from the Net::Async::FastCGI examples on metacpan.org. So kinda of run out of idea here...

Comment on Re^2: Benchmarking Perl's Net::Async::FastCGI app consistently return LOTS of "Non-2xx responses"

Replies are listed 'Best First'.
Re^3: Benchmarking Perl's Net::Async::FastCGI app consistently return LOTS of "Non-2xx responses" by Corion (Patriarch) on Dec 05, 2025 at 07:13 UTC
Maybe try reducing the concurrency to 1 and 2, just to see if you are at all able to have more than one request in flight at the same time?	[reply]
Re^4: Benchmarking Perl's Net::Async::FastCGI app consistently return LOTS of "Non-2xx responses" by Anonymous Monk on Dec 05, 2025 at 13:47 UTC
From ApacheBench result above, 15 out of 100 requests return a successful 200 OK code, while 85 of them return the 502 Bad Gateway.	[reply]