Hi All,
We have modperl application running on 64bit (2 cores), freebsd 8.2, perl
1.14.1, modperl 2.0.5, apache 2.2.21, 24GB of ram and about 5.5k users.
Additional system details are below. Under heavy load we are seeing errors
of the form
Failed to evaluate module Parser::Legacy: Attempt to r
please call my mobile number in the event of emergency.
From: Jason Aubrey [mailto:aubre...@gmail.com]
Sent: Wednesday, October 03, 2012 9:46 AM
To: modperl@perl.apache.org
Subject: reloading perl modules under heavy load
Hi All,
We have modperl application running on 64bit (2 cores), freebsd 8.2
On 10/3/2012 8:45 AM, Jason Aubrey wrote:
Hi All,
We have modperl application running on 64bit (2 cores), freebsd 8.2,
perl 1.14.1, modperl 2.0.5, apache 2.2.21, 24GB of ram and about 5.5k
users. Additional system details are below. Under heavy load we are
seeing errors of the form
Failed
> Hi All,
>
> We have modperl application running on 64bit (2 cores), freebsd 8.2, perl
> 1.14.1, modperl 2.0.5, apache 2.2.21, 24GB of ram and about 5.5k users.
> Additional system details are below. Under heavy load we are seeing errors
> of the form
>
> Failed to evaluate module Parser::Lega
On Wed, Oct 3, 2012 at 9:45 AM, Jason Aubrey wrote:
> Hi All,
>
> We have modperl application running on 64bit (2 cores), freebsd 8.2, perl
> 1.14.1, modperl 2.0.5, apache 2.2.21, 24GB of ram and about 5.5k users.
> Additional system details are below. Under heavy load we are seeing errors
> of
Thanks all for your replies to my question.
Because of the nature of our application, we can't really load everything
at start up, but I did some digging and there are clearly some
inefficiencies here and the situation would indeed be improved by cleaning
these up. However, it does look like it ma
On 4 October 2012 16:36, Jason Aubrey wrote:
> Thanks all for your replies to my question.
>
> Because of the nature of our application, we can't really load everything at
> start up, but I did some digging and there are clearly some inefficiencies
> here and the situation would indeed be improved
On Thu, Oct 4, 2012 at 10:36 AM, Jason Aubrey wrote:
> Now, we have MaxClients set super high
I hope you don't have it set so high that if you hit it you would run
out of memory and start swapping...
> Also possibly relevant is
> kern.ipc.somaxconn which "limits the size of the listen queue for
On Thu, Oct 4, 2012 at 9:53 AM, demerphq wrote:
> On 4 October 2012 16:36, Jason Aubrey wrote:
> > Thanks all for your replies to my question.
> >
> > Because of the nature of our application, we can't really load
> everything at
> > start up, but I did some digging and there are clearly some
>
