On Feb 18, 2008 4:40 AM, André Warnier <[EMAIL PROTECTED]> wrote: > What I have until now believed is that perl "code" is in fact "data" for > the perl interpreter, and that as such it cannot really be "shared". > What I mean is that, as soon as some bit is changed in a "page" of any > perl module, that "page" is dirty and must be copied and made private to > the one child process. And since there is (in my understanding) not such > a clear separation as to which parts in "perl code" are data and which > are code, after a while one ends up with a full duplicate in each child > anyway. Probably badly explained, but not so in the general sense ?
Your technical understanding is correct, but in practice most pages remain shared. You can help this by using a tool like Apache::SizeLimit that kills off processes after a while. - Perrin
