Joshua,
Thanks for the advice. I thought Apache::ASP was the cause of thrasing,
but you're right, the locking problem must be have been caused by an
overgrown swap file. I don't know what might have caused it. I just
rolled out the server (it's my first), today was the first day of
classes here at the university and it got hit hard. I guess I should have
tested it better. Well, back to the drawing board (er, testing board
:)...
Dmitry
On Tue, 11 Jan 2000, Joshua Chamas wrote:
> Dmitry Beransky wrote:
> >
> > Hi,
> >
> > A few hours ago, my server started threashing and I had to restart httpd.
> > When I looked at the error log, it was full of messages like those few
> > below. Any ideas what might have caused this?
> >
>
> A common reason for a mod_perl server to be thrashing is
> that the MaxClients was not set low enough, and your server
> got real busy for some reason. Always test your server
> running at MaxClients for a while to make sure that it
> can handle the setting.
>
> One way to simulate is with using ab, and setting it to
> a high concurrency level, and run that for a while on your
> nastiest of scripts. If this is an Apache::ASP script
> that uses sessions, this will also give the session
> manager a good workout, since ab will create one new session
> for each request, because it does not remember cookies.
>
> -- Joshua
> _________________________________________________________________
> Joshua Chamas Chamas Enterprises Inc.
> NodeWorks >> free web link monitoring Huntington Beach, CA USA
> http://www.nodeworks.com 1-714-625-4051
>
