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

Given the code the OP has supplied

That's the pertinent point. The OP has not supplied the full code so we can only guess as to what the rest of it is doing. Further, the fact that the durations reported are wallclock times means that any other process could also be interfering with the resultant durations reported.

That's not to say that your suggestion that the processes are IO-bound is wrong or even unlikely and I too suspect that this will turn out to be the limiting factor in the OP's case. But it is just an guess at this point even if an educated one.

Replies are listed 'Best First'.
Re^4: Problem in creating process
by BrowserUk (Patriarch) on Nov 23, 2015 at 11:59 UTC
    any other process could also be interfering with the resultant durations reported.

    But profiling (using any of the available perl profilers) won't delineate the affects of those others processors, so won't add to the information available.

    I too suspect that this will turn out to be the limiting factor in the OP's case. But it is just an guess at this point even if an educated one.

    I would say that:

    1. given the structure of the main loop;
    2. and that the child processes exit as soon as they have run their respective subroutines;
    3. And the full code of those subroutines is supplied.

    Unless the OP is deliberately hiding something from us; there is simply no scope for this to be anything other than an IO bound process.

    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.
[reply]

In Section Seekers of Perl Wisdom