On Tue, 18 Sep 2007, John L wrote:
Well, now I restarted it and the load is a reasonable 3 to 5. Must have been
a spam blast, will have to wait and see if it happens again.
I see a lot of plugins that read config files in the hook routines. Seems to
me that in forkserver, that means each fork will reread the file, and it'd be
faster if I read the config in the register routine and put the array into
$self->{_whatever} so it'll be inherited in the fork.
Sound reasonable? Each file is pretty small, but in aggregate there are a
lot of them.
Yes it's reasonable. I also have a sneaky feeling that caching of config
data is broken in 0.40 for various setups, but that's not that relevant
anyway under forkserver as each process will have to re-read the config if
it's not loaded before the fork.
Matt.
