The advice I've read is to spawn all your threads at startup time when the memory footprint is low ...

You can also spawn a thread factory early in your program before you load any modules. You can then load (require) the modules needed by your main thread, and when you need to spawn a thread, have the thread factory do it for you.

Each new thread created by the thread factory will be a duplicate of the first thread created with it's low(ish) memory footprint, rather than a duplicate of the main thread as would be the case if your spawned it from there.

With this technique, you can more cheaply create new threads, that only load what they individually need, as you need them rather than having to start them all at the beginning.

It is a shame the lengths you have to go to defeat the rediculous default behaviour :(

I hope Perl6 will include Java-like threads.

I hope that Perl6 will have both User threads (Java-like) and Kernel threads (Perl5-like iThreads--'cept without the enforced duplication).

Spawning an iThread should just start the function I pass it in a new interpreter running in a new system thread, and leave me to decide what to load there.

The User thread scheduler would be loaded as a module into one or more Ithreads and be scheduled cooperatively.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
The "good enough" maybe good enough for the now, and perfection maybe unobtainable, but that should not preclude us from striving for perfection, when time, circumstance or desire allow.

In reply to Re^2: Threading vs perl by BrowserUk
in thread Threading vs perl by Eyck

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.