Forum: Rails deployment stress testing software

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
5e8fd591aeccbffd6fc93c171ac4fa43?d=identicon&s=25 Aaron Smith (warhero)
on 2007-06-28 07:30
anyone know of a pretty basic simple to use stress testing software? I'm
not using it specifically for rails stress testing. So something that
can be configured to do any http requests??

Ee7052b87b82257740f232a958c3d49e?d=identicon&s=25 Steve Tooke (Guest)
on 2007-06-28 11:29
(Received via mailing list)
httperf -

Zed Shaw talks about using it with rails/mongrel here:


On Jun 28, 6:30 am, Aaron Smith <>
10c122532c00465b809dbf9dc35806a7?d=identicon&s=25 Paolo Negri (Guest)
on 2007-06-28 14:07
(Received via mailing list)
wbox is an alternative

5e8fd591aeccbffd6fc93c171ac4fa43?d=identicon&s=25 Aaron Smith (warhero)
on 2007-06-28 15:33
Paolo Negri wrote:
> wbox is an alternative
> Paolo

thanks man, this looks promising.
38a02bf7121a81be5be6f3d488ce23b5?d=identicon&s=25 Alexey Verkhovsky (Guest)
on 2007-06-28 17:33
(Received via mailing list)
Depends on how complex your simulation needs to be. If you are looking
to test your infrastructure, something like httperf or wbox is
entirely adequate, and very easy to use.

If you need to simulate a mix of user session scenarios, jMeter or
Grinder are more suitable for that. Doing this generally makes sense
when you are going to hit high load levels from day one (e.g.,
replacing a legacy app). You should also take every opportunity to
find and fix performance problems in quick and dirty ways (with
httperf), before going for complex simulations.

B4ec694f9d955bee753559037aa1805a?d=identicon&s=25 Nathan Clark (Guest)
on 2007-07-01 03:17
(Received via mailing list)
try jmeter.


On Jun 28, 12:30 am, Aaron Smith <>
This topic is locked and can not be replied to.