Re: reloading modules in a handler with eval

2004-02-27 Thread Mark Maunder
I forgot about that. I guess once all Apache kids exist, there's no way to overwrite that module in shared memory without restarting Apache? Silly question I guess. That's why they call it copy-on-write. mark. On Fri, 2004-02-27 at 13:15, Perrin Harkins wrote: > Mark Maunder wrote: > > For what I

Re: reloading modules in a handler with eval

2004-02-27 Thread Mark Maunder
Thanks for this Charles. I've never heard of vmstat, and after playing with it for a few mins am amazed at my ignorance and its usefulness. On Fri, 2004-02-27 at 21:07, Charles C. Fu wrote: > In <[EMAIL PROTECTED]> on 27 Feb 2004, >Mark Maunder <[EMAIL PROTECTED]> wrote: > > Anyone know if the

Re: reloading modules in a handler with eval

2004-02-27 Thread Charles C. Fu
In <[EMAIL PROTECTED]> on 27 Feb 2004, Mark Maunder <[EMAIL PROTECTED]> wrote: > Anyone know if the linux filesystem cache caches directory > information. I.e., does a stat by apache guarantee disk access? This is almost certainly filesystem dependent; but for the usual filesystems (ext2, ext3,

Re: reloading modules in a handler with eval

2004-02-27 Thread Perrin Harkins
Mark Maunder wrote: For what I'm doing the only performance hit is the stat() on every module The other performance hit is that the memory used by these modules is no longer shared by copy-on-write. - Perrin -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/

Re: reloading modules in a handler with eval

2004-02-27 Thread Mark Maunder
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 di

Re: reloading modules in a handler with eval

2004-02-27 Thread David R. Baird
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 fi

Re: reloading modules in a handler with eval

2004-02-27 Thread Tom Schindl
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. Nevertheless I don't know exactly how Apache::Reload is working but I suppose it deletes the module in %INC and reloads it using perls standa

Re: reloading modules in a handler with eval

2004-02-27 Thread Thomas Klausner
Hi! On Fri, Feb 27, 2004 at 09:35:11AM +, Mark Maunder wrote: > In a perl handler, I'm doing a stat on a module file, and if the file > has been modified, I'm reloading the module by slurping the file into a > scalar and eval'ing it. The module has a few subs and global vars that > have defau

reloading modules in a handler with eval

2004-02-27 Thread Mark Maunder
Hi, In a perl handler, I'm doing a stat on a module file, and if the file has been modified, I'm reloading the module by slurping the file into a scalar and eval'ing it. The module has a few subs and global vars that have defaults set on initialization. I have about 20 modules I'm doing this with