I've been trying your optimized code on my machine (an old Duron 700MHz, under medium load):
$ time ./bench.pl
187692
real 17m12.507s
user 10m3.640s
sys 0m1.300s
so it's still
very slow compared to what it does.
Then, I've tried to compile it:
$ perlcc -O -o bench bench.pl
$ time ./bench
187692
real 12m35.665s
user 6m1.480s
sys 0m0.720s
It still is definitely slow, but you get an evident boost in
performance just by compiling it into C code... something to remember for situations in which you really need Perl for doing lengthy tasks.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.