Re^2: ithreads weren't the way.. still searching

in reply to Re: ithreads weren't the way.. still searching
in thread ithreads weren't the way.. still searching

You're right, of course.. I'm trying to make the best out of this, but there's definitely not too much to gain - profiling the code showed about 2 secs of processing in 18 of execution. But it seemed like an interesting situation. The ithreads limitations found *seemed* real (BrowserUk) =), and I wondered how to do what I set myself to at first, should I find myself in a similar position where real gain was at stake. Thanks

Comment on Re^2: ithreads weren't the way.. still searching

Replies are listed 'Best First'.
Re^3: ithreads weren't the way.. still searching by BrowserUk (Patriarch) on Oct 01, 2004 at 04:34 UTC
If you use a machine gun to beat the enemy over the head... Examine what is said, not who speaks. "Efficiency is intelligent laziness." -David Dunham "Think for yourself!" - Abigail "Memory, processor, disk in that order on the hardware side. Algorithm, algorithm, algorithm on the code side." - tachyon	[reply] [d/l]

In Section Seekers of Perl Wisdom