Re: [mp2] perl_clone takes 5 and more seconds to complete

[Elizabeth Mattijsen]

At 10:58 -0500 11/12/03, Geoffrey Young wrote:
Rafael Garcia-Suarez wrote:
Geoffrey Young wrote:
the problem with this, though, is that we don't really want a 
clean interpreter, we want an _almost_ clean one - one with only 
the data we know is important (like the globals set within the 
<Perl> section).  so, if we could copy the relevant data from the 
first interpreter and insert it into the one we're about to clone 
for the request, we'd have the best situation possible - minimal 
data in the parent interpreter.
Problem : how to separate the relevant data from the irrelevant one ?
Does it live in a particular package ?
for the <Perl> stuff I was talking about, I believe so.  however, 
for directive handlers it does not, so we'd probably need to tweak 
the interface  a bit.
but the idea, I guess, is that mod_perl would (eventually) know what 
data is required to be copied, so long as we had a way to do it.
Wouldn't Storable or Data::Dumper be able to do such a thing?  At the 
end of config, dump the pertinent bits to memory (or possibly even a 
file), and then read them back in the other interpreter?

Liz

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]