On 05/20/2010 08:54 AM, Some Guy wrote:
The cleanup handler is a brilliant idea. That removes the need for a polling thread. If I attach the cleanup to the request's pool and run in a threaded MPM, this led to contention for the globals that I'm updating in C. Is this the case with PerlModules, or can I get away without locking them?
Why use a threaded MPM? Is there something else you're running that relies on it? We generally recommend doing with the prefork mpm because you're running in share-nothing mode which performs better (and uses less memory on decent operating systems).
-- Michael Peters Plus Three, LP
