I think that would be a better route. Even commercial compiled programs
can’t generate that many parallel requests. Mercury LoadRunner, for
instance, can only create about 20 to 25 virtual users per
single-processor desktop-class computer. The load tests I’ve seen/done
tend to create stress by increasing the number of bytes or requests per
second rather than the number of concurrent requests.
Al
···
-----Original Message-----
From: E F van de Laar [mailto:emiel@il.fontys.nl]
Sent: Wednesday, February 26, 2003 12:51 AM
To: ruby-talk ML
Subject: Re: Ruby in Performance Testing
- Tim Bates (tim@bates.id.au) wrote:
On Wed, 26 Feb 2003 6:57 pm, E F van de Laar wrote:
Does anyone have any other approaches for this kind of test? Is ruby
not up to this sort of task? Would fork be a better approach?
How do I raise this limit? Any tips are welcome.I know this is a Ruby list, but if you use Apache it comes bundled
with a
program called ‘ab’ (Apache Benchmark) which does load testing with
any
number of concurrent requests. You may wish to take a look at it.
I’m aware of “ab” but this is a custom tcp server. Not a web server.
Requests are made up of a custom format. Though it might not be a bad
idea to modify “ab” or “siege” to do this for me.
Thanks,
Emiel
E F van de Laar
+31648183479
www.il.fontys.nl/~emiel