Dear Alceu,

I don't *think* the overhead of compiling with threads on is a big issue for code that does not use threads. I am open to correction on that of course :-) I do have both a threaded and non-threaded available. Maybe I can test at some point.

I've had to jump thru' hoops to get my *threaded* performance (I mean - in a genuinely threaded application) up to scratch though (bascially reducing the memory footprint per thread) because it clones the environment in the new thread, including loaded modules, and so on. But I do have threaded Perl apps that run with 100's of threads just fine.

But, again, if you don't actually *use* threads, I'm not sure that matters.

Kind regards

Derek.

In reply to Re^3: AIX vs. Linux memory use by scunacc
in thread AIX vs. Linux memory use by scunacc

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.