For what I'm doing the only performance hit is the stat() on every module, which means disk access. That's 20 stats per request because there are 20 modules. The 'touch' option means only one stat instead of 20. Much better.
Moving slightly OT. Anyone know if the linux filesystem cache caches directory information. I.e., does a stat by apache guarantee disk access? Or only if the file info isn't in the OS cache. I know mysql relies heavily on the OS filesytem cache. Does Apache get any benefit from it? On Fri, 2004-02-27 at 11:09, David R. Baird wrote: > On 27 Feb 2004 at 11:22, Tom Schindl wrote: > > > I go with you in a dev environment still it decreases performance so > > on a production server where modules should not change every minute I > > never use it. > > >From the Apache::Reload docs: > > ---------- > Special "Touch" File > > You can also set a file that you can touch() that causes the > reloads to be performed. If you set this, and don't touch() > the file, the reloads don't happen. This can be a great boon > in a live environment: > > PerlSetVar ReloadTouchFile /tmp/reload_modules > > Now when you're happy with your changes, simply go to the > command line and type: > > touch /tmp/reload_modules > > And your modules will be magically reloaded on the next > request. > ---------- > > You can also explicitly register the modules you want to be > reloadable: > > PerlInitHandler Apache::Reload > PerlSetVar ReloadAll Off > PerlSetVar ReloadModules "My::Foo My::Bar Foo::Bar::Test" > > > HTH. > > -- > Dr. David R. Baird > ZeroFive Web Design > [EMAIL PROTECTED] > http://www.zerofive.co.uk -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
