Alas, that doesn't solve my problem.

(If you peek a bit deeper into Use more threads., you'll see my comments/efforts in that regard)

My problem is that I've got big objects residing in an apartment thread. (btw, I am using an editbin'd perl w/ only 32K stack reserve). I've injected enough print's while monitoring process size to see that each thread is chewing up 9-10 meg, much of it due to DBI + a big pure Perl DBD. Having played with the various embedded data in the DBD, I know its the ithreads cloned bytecode thats sucking up all the RAM.

With iCOW, my hunch/hope is the incremental per-thread growth would drop drastically.

In reply to Re^2: Whence iCOW ? by renodino
in thread Whence iCOW ? by renodino

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.