an up-front single request for as many pages of VM as are required followed by a single ring 3 rep mov.
I don't think so. Each variable should be copied separately, and you have to fix the references. So it's much more than single memory allocation.
Yes. That is an annoying detail of the ithreads implementation. But, it is quite easy to avoid; you just spawn your workers early, and have them require rather than use what they (individually) need.
Sorry, don't see how this can help. Workers usually all need the same set of modules.
In reply to Re^13: Strange memory leak using just threads (forks.pm)
by zwon
in thread Strange memory leak using just threads
by MnkyBrain
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |