Re: fork(): where does copy happen?

If you're on Linux, the Linux::SMAPS module can help you tell how much is shared. It's impossible to keep it all shared, but your hash access is certainly not helping. Avoiding conversions between strings and numbers is also good.

Comment on Re: fork(): where does copy happen?

Replies are listed 'Best First'.
Re^2: fork(): where does copy happen? by Anonymous Monk on Apr 16, 2008 at 14:34 UTC
thanks, this sounds really interesting. sadly there are no smaps-files on our server, which has kernel 2.6.8. Do I need special kernel versions or options to use this? On my desktop (kernel 2.6.22) these files are available...	[reply]
Re^3: fork(): where does copy happen? by Hue-Bond (Priest) on Apr 16, 2008 at 15:13 UTC
You need 2.6.14 at least. -- David Serrano	[reply]
Re^4: fork(): where does copy happen? by Anonymous Monk on Apr 16, 2008 at 15:36 UTC
ok, found a server with 2.6.18 having the smaps files! thanks all, I will try my luck with smaps now :)	[reply]
Re^4: fork(): where does copy happen? by Anonymous Monk on Apr 16, 2008 at 16:46 UTC
i found a server with a kernel which matches the requirements and has smaps... I'll play with it the next days :)	[reply]