But since both does the same cleanup and join() does it at a later stage - I think both should have the same memory efficiency

If you do:

my $a = async { ... }; ... some other stuff; my $b = async { ... }; $_->join for $a, $b;

Your peak memory usage may be slightly higher than if you do:

async { ... }->detach; ... some other stuff; async { ... }->detach;

Because the second thread will require the process to allocate more virtual memory to accomodate the stack space for the second thread, because the first thread hasn't been joined when it is created.

Whereas, with the second snippet, the first thread may have completed before the second thread is created, and so the memory used by the first thread can be reused for the second. Thereby the total memory consumption may be a little lower. It's all a matter of timing.

If total memory consumption isn't a problem, just ignore it.

I'd still want to investigate the DBI error though. It is likely also a timing problem.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^3: join() or detach() which is more memory efficient ? by BrowserUk
in thread join() or detach() which is more memory efficient ? by goutamram

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.