Hello,
The documentation for ModPerl::Registry states: Note that each httpd
process or child must compile each script once, so the first request
to one server may seem slow, but each request there after will be
faster. If your scripts are large and/or make use of many Perl modules,
this
I don't know about ModPerl::RegistryLoader, but the simplest solution is just
to preload the interpreters either manually or through a script whenever you
restart Apache. In your httpd.conf file, you control how many interpreters are
running and how many hits each interpreter handles before
2011/7/21 Jiří Pavlovský j...@getnet.cz:
So I was looking a solution and found ModPerl::RegistryLoader. I'm just not
sure I understand it completely. Is this the compile once at startup
solution?
Yes, that's what it's for.
Do I just put my $rlbb = ModPerl::RegistryLoader-new(); into
my
On 21.7.2011 18:41, Perrin Harkins wrote:
So I was looking a solution and found ModPerl::RegistryLoader. I'm just not
sure I understand it completely. Is this the compile once at startup
solution?
Yes, that's what it's for.
Thanks, so I'm on correct track
Do I just put my $rlbb =
Author: phred
Date: Thu Jul 21 15:34:31 2011
New Revision: 1149225
URL: http://svn.apache.org/viewvc?rev=1149225view=rev
Log:
[rt.cpan.org #69643] [PATCH] Spelling fix
Modified:
perl/Apache-Reload/trunk/lib/Apache2/Reload.pm
Modified: perl/Apache-Reload/trunk/lib/Apache2/Reload.pm
URL:
Author: phred
Date: Thu Jul 21 15:41:54 2011
New Revision: 1149233
URL: http://svn.apache.org/viewvc?rev=1149233view=rev
Log:
69643
Modified:
perl/Apache-Reload/trunk/Changes
Modified: perl/Apache-Reload/trunk/Changes
URL:
