renodino has asked for the wisdom of the Perl Monks concerning the following question:

I'm trying to track down detailed info on iCOW, but Google and Maillist Archive aren't surfacing much of use...(unless its the eagerly anticipated establishment of the International Centre of Woodchuck Studies).

Can anyone point me to a resource or 2 ? I'm pushing perl threads to the limits of memory with a large scale app, and suspect that iCOW would let me squeeze in a lot more threads. Current performance is fine, and there's plenty of CPU headroom left for more processing; its just the scalability limits imposed by memory that are problematic.

Replies are listed 'Best First'.
Re: Whence iCOW ?
by beachbum (Beadle) on Mar 07, 2006 at 22:13 UTC
[reply]
      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.

[reply]
Re: Whence iCOW ?
by dave_the_m (Monsignor) on Mar 07, 2006 at 22:59 UTC
    iCOW is still on my big list of things to do (and on my list of big things to do).

    I still haven't resolved all the issues in my head yet, and once I've done that I need to find a major chunk of time to do some coding.

    Dave.

[reply]
Re: Whence iCOW ?
by Fletch (Bishop) on Mar 07, 2006 at 18:36 UTC

    Probably the best bet would be to ask on perl5porters; someone working on it would most likely be watching that list.

[reply]

Back to Seekers of Perl Wisdom