> At 06:11 AM 11/10/00 -0500, barries wrote:
> >> Address Kbytes Resident Shared Private
> >> -------- ------ -------- ------ -------
> >> total Kb 24720 22720 3288 19432 <<< pre-loaded modules
> >> total Kb 14592 12976 3096 9880 <<< not pre-loaed modules.
>
> When looking at pmap it looks like the main difference in "private" memory
> usage is in the heap. I'm not clear why the heap would end up so much
> bigger when pre-loading modules.
A guess: When pmap says "shared" it means stuff that realy shared.
I.E. it's not counting stuff that is marked copy-on-write, which is
shared UNTIL YOU TRY TO MODIFY IT.
Using pre-loaded modules you will get some things (XS) mmaped in as
shared, read-only and a whole bunch of stuff loaded into the heap.
this is "shared" when you fork, until you change it.
The trick is that most of the perl "bytecode" doesn't get modified after
it's loaded, so it'll stay "shared".
--
John Hughes <[EMAIL PROTECTED]>,
CalvaEDI SA. Tel: +33-1-4313-3131
66 rue du Moulin de la Pointe, Fax: +33-1-4313-3139
75013 PARIS.
