4 ms·
See also Siege (https://www.joedog.org/siege-home/ https://www.joedog.org/siege-home/)
by otterley 12y ago
See also Siege (https://www.joedog.org/siege-home/ https://www.joedog.org/siege-home/)
- troels 12y agoI've been a fan of siege, but recently I had to test an app under very high load and I had big trouble getting siege to do that. The default ubuntu install has some hard limits on file pointers and compiling it from source seemed to segfault all the time. I ended up switching over to httperf.
- ecdavis 12y agoI used Siege a few years ago for some benchmarking and was not impressed. It's a pity because I really like the interface, but Siege is technically lacking. There is a warning in the configuration file against using keep-alive with no explanation as to why. That makes it useless when you need to benchmark persistent connections. Each Siege "user" (i.e. client) has it's own thread, which means they consume a large number of resources. Depending on your CPU, you will also hit a point where more time is spent switching between threads than actually sending requests. I wasn't able to exceed 400 users on my 2011 test machine. That makes it useless when you need to benchmark large numbers of connections.