Hmm, randomization is a bit different, yes, but it is open-loop in the sense that it doesn’t care about how well does the server respond to the requests, it just sends as many requests as specified. Connection count in this case entirely depends on how well the server is responding, if it’s time to send a new request and all of the existing connections are waiting for a response, it opens up a new connection and sends a request there.
Adding some noise generation options to it would be nice though, and possibly quite easy.
If anyone knows a HTTP benchmark / stress-test tool that is an open loop system let me know. (
wrkand all the others like it are closed loop systems.)I’ve been using vegeta for HTTP benchmarking and stress testing, it is a very nice and simple open loop system.
How does this tool achieve the “open loop system” requirements?
Because, it should at least support the following features (which I don’t see mentioned in the readme, at least at a quick glance):
Based on the arguments supported by the tool, it follows exactly the same model as
wrk.Hmm, randomization is a bit different, yes, but it is open-loop in the sense that it doesn’t care about how well does the server respond to the requests, it just sends as many requests as specified. Connection count in this case entirely depends on how well the server is responding, if it’s time to send a new request and all of the existing connections are waiting for a response, it opens up a new connection and sends a request there.
Adding some noise generation options to it would be nice though, and possibly quite easy.