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 testing. > The response time of the server is roughly > constant but we observe some pretty high spikes in the latency every 30 > seconds or so, as if the server was interrupted for a short period of > time (approx. 300 ms). The delay of 300 ms seems very high for tasks > like shared memory accesses or garbage collection Perl doesn't do garbage collection like Java does. There wouldn't be any shared memory either, unless you are doing it in your own code. What you're describing sounds more like running out of memory and going into swap or killing off all the apache processes at once and having to spawn new ones. You haven't given us much to go on here. Can you post the relevant sections of your conf file(s) (i.e. not the boilerplate stuff) and some of your code? - Perrin -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
