Hi,
in a prefork enviroment you would need to use MaxRequestsPerChild, not sure how this is named in a threaded environment. MaxKeepAlive is something different.
Gerald
From: Brett @Google [mailto:brett.maxfield@gmail.com]
Sent: Thursday, February 04, 2010 3:10 AM
To: Gerald Richter - ECOS
Subject: Re: threaded Embperl / mod_perl2
Hi Gerald,
I think a temporary solution is to stop the content switch probing so often, but maybe i am only deferring the problem.
MaxKeepAliveRequests was 100, now it is 20. But i am not sure this will help.
I think somehow i have a threaded perl, but a non-threaded apache/mod_perl/Embperl. Do you think this would be bad, i did not think so, i need a threaded perl for other application on this box. I thought it would be harmless.
I have also a bug with regards to EMBPERL_LOG if you are interested, it opens the file for writing as root that the server starts as, not the non-root user that the apache prefork workers run as. However it then tries to reads/appends as the apache user, so the file created cannot be appended by the apache user, even if it was created by the same apache execution.
Workaround is to create file writable by the apache user first.
Cheers
Brett
On Thu, Feb 4, 2010 at 3:08 AM, Gerald Richter - ECOS <gerald.richter@ecos.de> wrote:
Hi,
also Embperl is written with threads in mind, there are some places, which might cause raise conditions, so Apache may crash when using threads.
Also I spent a lot of time in solving memory leaks for Embperl, there are some Problems in Perl itself when redefining code. I guess this is the reason for the increasing memory usage you see. I don’t have solution for this, because the problem is in the Perl core. The only solution I see, it to limit the number of request per Perl interpreter.
I currently have no need for Embperl using threads, so I will not implement it, unless somebody pays me for it or I get a project where I need it
Regards
Gerald
From: Brett @Google [mailto:brett.maxfield@gmail.com]
Sent: Wednesday, February 03, 2010 5:49 AM
To: Gerald Richter
Subject: threaded Embperl / mod_perl2
Hi Gerald,
Is Emperl for mod_perl2 ever likely to support threads in a "supported" sense ?
I ask because i tried it anyway (although it's not recommended), and it seems to work in the short term, but it seems to have a memory leak or problem such that large number of connections over about a day cause some sort of resource issue and the Apache in which it runs becomes unresponsive.
This is behind a content switch which probes every 10-ish seconds, with a full connection. It does not happen in my dev region, which does not have a content switch, so i am assuming it is due to the large number of connection over time. Plain old users (at least for single user test traffic) is not enough to expose the problem.
This is running on solaris sparc, 64 bit compiler under Sun Studio 12.
Cheers
Brett
in a prefork enviroment you would need to use MaxRequestsPerChild, not sure how this is named in a threaded environment. MaxKeepAlive is something different.
Gerald
From: Brett @Google [mailto:brett.maxfield@gmail.com]
Sent: Thursday, February 04, 2010 3:10 AM
To: Gerald Richter - ECOS
Subject: Re: threaded Embperl / mod_perl2
Hi Gerald,
I think a temporary solution is to stop the content switch probing so often, but maybe i am only deferring the problem.
MaxKeepAliveRequests was 100, now it is 20. But i am not sure this will help.
I think somehow i have a threaded perl, but a non-threaded apache/mod_perl/Embperl. Do you think this would be bad, i did not think so, i need a threaded perl for other application on this box. I thought it would be harmless.
I have also a bug with regards to EMBPERL_LOG if you are interested, it opens the file for writing as root that the server starts as, not the non-root user that the apache prefork workers run as. However it then tries to reads/appends as the apache user, so the file created cannot be appended by the apache user, even if it was created by the same apache execution.
Workaround is to create file writable by the apache user first.
Cheers
Brett
On Thu, Feb 4, 2010 at 3:08 AM, Gerald Richter - ECOS <gerald.richter@ecos.de> wrote:
Hi,
also Embperl is written with threads in mind, there are some places, which might cause raise conditions, so Apache may crash when using threads.
Also I spent a lot of time in solving memory leaks for Embperl, there are some Problems in Perl itself when redefining code. I guess this is the reason for the increasing memory usage you see. I don’t have solution for this, because the problem is in the Perl core. The only solution I see, it to limit the number of request per Perl interpreter.
I currently have no need for Embperl using threads, so I will not implement it, unless somebody pays me for it or I get a project where I need it
Regards
Gerald
From: Brett @Google [mailto:brett.maxfield@gmail.com]
Sent: Wednesday, February 03, 2010 5:49 AM
To: Gerald Richter
Subject: threaded Embperl / mod_perl2
Hi Gerald,
Is Emperl for mod_perl2 ever likely to support threads in a "supported" sense ?
I ask because i tried it anyway (although it's not recommended), and it seems to work in the short term, but it seems to have a memory leak or problem such that large number of connections over about a day cause some sort of resource issue and the Apache in which it runs becomes unresponsive.
This is behind a content switch which probes every 10-ish seconds, with a full connection. It does not happen in my dev region, which does not have a content switch, so i am assuming it is due to the large number of connection over time. Plain old users (at least for single user test traffic) is not enough to expose the problem.
This is running on solaris sparc, 64 bit compiler under Sun Studio 12.
Cheers
Brett