Rici Lake wrote:
In the course of trying to figure out why mod_info does not reveal directives added in PerlSections (see other email), I stumbled across the following problem:
I created a simple seven-line .htaccess file, and did 100,000 requests to a file in the corresponding directory with ab. All processes were perfectly stable in memory consumption. Then I do the same thing with a <Perl> section in the .htaccess file. 100,000 requests later my 12 processes had grown from 6.5M to 25.5M
Could you please post the 2 .htaccess files you've been using ?
My analysis of this is that mod_perl's perl sections are *always* run in the pconf pool, rather than running in the request pool as would be normal for .htaccess files. Consequently, all directive parsing and config merging will use the pconf pool, effectively resulting in a permanent expansion of that pool.
Hrm, that's quite odd, as I looked over the code and AFAIK, <Perl> sections in .htaccess will be running off parms->pool, and in the case of .htaccess files, that's r->pool. Can you tell me more about how you made the determination that it was using the pconf ?
-- -------------------------------------------------------------------------------- Philippe M. Chiasson m/gozer\@(apache|cpan|ectoplasm)\.org/ GPG KeyID : 88C3A5A5 http://gozer.ectoplasm.org/ F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3A5A5
signature.asc
Description: OpenPGP digital signature
