Hence the existence of forks.pm. It has the improved efficiency of creating a new "thread" because it uses fork() to do that
Sure, fork will be faster. But on any process long-running enough to be worth multi-threading, 0.01 per core is but a drop in the ocean.
How long will it take to
And I bet that establishing those socket connections more than negates the lower start-up cost of fork.
Which timing is the more important?
In reply to Re^8: Strange memory leak using just threads (forks.pm)
by BrowserUk
in thread Strange memory leak using just threads
by MnkyBrain
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |