in reply to Re^3: Problem in creating process
in thread Problem in creating process

I believe that hippo is suggesting that he should have profiled the original.

The OP timed both approaches; the single tasking version was faster than his attempt at multitasking. That is about as much information as you can hope to derive from profiling this kind of process.

Ie. For the single tasking approach, reading a record takes maybe 5 to 10 times longer than processing that record. No matter how much you speed up the processing code, the IO time which dominates won't change.

Ie. If the ratio between IO and processing is 10:1, the absolute best improvement he could get is a 10% saving by not performing that processing.

The parallel approach appears to be a 'guess'.

What is the difference between a "guess" and a 'trial', or an 'experiment'; or a 'test'?

And how will profiling the single tasking version inform the user such that he can avoid performing some trials, tests or experiments to improve his processing time?

The only guess here is that kneejerk response of "profile it" in response to any question that mentions "improving performance".

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
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". I knew I was on the right track :)
In the absence of evidence, opinion is indistinguishable from prejudice.

In Section Seekers of Perl Wisdom