Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Benchmarking perls 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Some other things on the other hand are much slower, most notably regexes (almost by a factor 2 when comparing 5.5.4 with a threaded 5.8.6).
    If I may just take one uninformed guess on the cause: Unicode. Internal Unicode support was added starting with 5.6.0.
    • Internal Unicode support was added starting with 5.6.0.

      Ah, that's plausible. I was also thinking of possible causes for this decrease in performance but didn't think of the obvious case.

      And the additional slow-down caused by threads is then also fairly obvious: Perl's regex engine, which is very non-reentrant by nature, has to work more reentrantly now.

      Other than that, I agree with mir's comment that with all the new features and bugfixes, the results are very favourable for perl and its porters. I always assumed perl had gotten slower (due to bloat) but for programs running in the wild (and not in a benchmark laboratory) the opposite is true.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.