On Tue, 2004-04-13 at 04:17, Pascal Felber wrote:
> It is mostly the default apache 2.0.48 configuration. I am using prefork
> MPM, with the following parameters:
>
> StartServers 5
> MinSpareServers 5
> MaxSpareServers 10
> MaxClients 150
> MaxRequestsPerChild
Perrin Harkins wrote:
> On Thu, 2004-04-08 at 11:48, Pascal Felber wrote:
> > The server is a [EMAIL PROTECTED]
> > 512MB, running linux 2.4.18-3, Apache 2.0.48, and mod_perl 1.99_08.
>
> That came out more than a year ago. You should be running
> the latest (1.99_13 at the moment) if you're go
On 8 Apr 2004, at 16:48, Pascal Felber wrote:
We have noticed some "strange" behavior when stress-testing one of our
perl modules and we haven't managed to find an explanation or
workaround
in the mod_perl documentation. We have reproduced this problem with a
minimal module, installed as a PerlRe
Perrin Harkins wrote:
On Thu, 2004-04-08 at 11:48, Pascal Felber wrote:
The server is a [EMAIL PROTECTED]
512MB, running linux 2.4.18-3, Apache 2.0.48, and mod_perl 1.99_08.
That came out more than a year ago. You should be running the latest
(1.99_13 at the moment) if you're going to do this k
On Thu, 2004-04-08 at 11:48, Pascal Felber wrote:
> The server is a [EMAIL PROTECTED]
> 512MB, running linux 2.4.18-3, Apache 2.0.48, and mod_perl 1.99_08.
That came out more than a year ago. You should be running the latest
(1.99_13 at the moment) if you're going to do this kind of stress
testin
We have noticed some "strange" behavior when stress-testing one of our
perl modules and we haven't managed to find an explanation or workaround
in the mod_perl documentation. We have reproduced this problem with a
minimal module, installed as a PerlResponseHandler, that simply sends am
HTTP 302 red
