I've got 4 new machines coming in around the 22nd. I'll have physical
access to them for two weeks before we colo them. Probably the easiest
way to determine mod_perl's scalability by going to multiproc on linux
would be for me to test them. They are dual proc machines, but I can pull
a proc out of them for testing pretty easily durring the two weeks that we
have them here.
Thoughts?
recomended scripts?
methods?
As for ab being coarse, I'm not sure I'd agree totaly with that. It
allows a fairly good amount of control. There is also once called
sslclient that is actually worse except it does ssl.
Scott
On Thu, 4 Jan 2001, Blue Lang wrote:
> On Thu, 4 Jan 2001, Roger Espel Llima wrote:
> > JR Mayberry <[EMAIL PROTECTED]> wrote:
> > > Linux does serious injustice to mod_perl. Anyone who uses Linux knows
> > > how horrible it is on SMP, I think some tests showed it uses as litle as
> > > 25% of the second processor..
> > A simple benchmark with 'ab' shows the number of requests per second
> > almost double when the concurrency is increased from 1 to 2. With a
> > concurrency of 4, the number of requests per second increases to
> > about 3.2 times the original, which is not bad at all considering
> > that these are dynamic requests with DB queries.
> Eh, ab isn't really made as anything other than the most coarsely-grained
> of benchmarks. Concurrency testing is useless because it will measure the
> ratio of requests/second/processor, not the scalability of requests from
> single to multiple processors.
