Re^3: Why is Windows 100 times slower than Linux when growing a large scalar?

No really. Could you point me to the "performance test suite" please? My searches haven't located anything likely.

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".

In the absence of evidence, opinion is indistinguishable from prejudice.

RIP PCW It is as I've been saying!(Audio until 20090817)

Comment on Re^3: Why is Windows 100 times slower than Linux when growing a large scalar?

Replies are listed 'Best First'.
Re^4: Why is Windows 100 times slower than Linux when growing a large scalar? by Anonymous Monk on Dec 03, 2009 at 03:43 UTC
Perl benchmark suite -------------------- This is a Perl benchmark suite. It can be used to compare the relative speed of different versions of Perl. You run the benchmark by starting the 'perlbench-run' script giving the path-name of various Perls you want to test as argument. The perlbench-run program takes the following optional parameters: -s don't scale numbers (so that first perl is always 1 +00) -t <filter> only tests that match <filter> regex are timed -c <cpu-factor> use this factor to scale tests instead of running t +he 'cpu_factor' program to determine it. -d <dirname> what directory to save results in [download] http://www.cpan.org/authors/id/GAAS/perlbench-0.93.readme	[reply] [d/l]

Replies are listed 'Best First'.

Re^4: Why is Windows 100 times slower than Linux when growing a large scalar?
by Anonymous Monk on Dec 03, 2009 at 03:43 UTC

Perl benchmark suite
--------------------

This is a Perl benchmark suite.  It can be used to compare the
relative speed of different versions of Perl.  You run the benchmark
by starting the 'perlbench-run' script giving the path-name of various
Perls you want to test as argument.  The perlbench-run program takes
the following optional parameters:

  -s               don't scale numbers (so that first perl is always 1
+00)
  -t <filter>      only tests that match <filter> regex are timed
  -c <cpu-factor>  use this factor to scale tests instead of running t
+he
                   'cpu_factor' program to determine it.
  -d <dirname>     what directory to save results in
[download]

[reply]
[d/l]