in reply to Perl -de1 weirdness.

Given the "P:\test>perl" I would think the blockiness comes from Windows doing something else, causing Perl to wait.

It might be interesting to run under the debugger in several DOS windows: set each to loop long enough that you can switch windows and start the others.

Send the output to file, process with "uniq".

Append a tag (a, b, c...) to each line, merge and sort the files. I'd guess the uniq'd, merged, sorted file would be similarly blocky, but that the lines would be close to a, b, c order.

Replies are listed 'Best First'.
Re^2: Perl -de1 weirdness.
by BrowserUk (Patriarch) on Jul 19, 2004 at 19:56 UTC

    Please note that both tests are running on the same system, using the same version of perl. The *only* difference is the use of the perl debugger.

    Besides which, if it were "windows making perl wait", the times would get spread wider apart, not grouped together in bunches. The latter effect suggests that perl is calling gettimeofday() more frequently that the timer is running.

    Given the timer is running 3,579,545 times a second, to produce the list of 30 consequetively identical times, The debugger would have to be running the loop 90 million times a second. Which would be nice, but I think we may have to wait for P7 to achieve that kind of performance :)

    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, algoritm, algorithm on the code side." - tachyon
[reply]

In Section Seekers of Perl Wisdom