in reply to threads memory usage...

threads and Coro are distinctly different. Coro only implements cooperative multithreading and will never use more than one CPU.

threads by design copies all data from the main thread, so the best approach is to spawn your worker threads as soon as possible and only then allocate data per-thread.

There is lots of discussion of threads and Coro here - Super Search will likely find these for you.

Replies are listed 'Best First'.
Re^2: threads memory usage...
by ratoa (Initiate) on Jun 06, 2011 at 18:31 UTC
    to Corion: thank you :p
    now I get it, I've been stuck between writing non-blocking method for <Coro> and reducing <threads> memory usage.
    still, it would great if someone can combine the advantage from the both :(
[reply]

In Section Seekers of Perl Wisdom