The problem with your benchmark is the calculation moves into floating point exception handling very early on.
If you avoid that by adding logs, using threads improve performance by 65%:
#! perl -slw
use strict;
use threads;
use Time::HiRes qw[ time ];
{
my $start = time;
my $t = 0;
$t += log( $_ ) for 230000..900000;
printf "%.15f\n", $t;;
printf "Took %.6f\n", time() - $start;
}
{
my $start = time;
my $thr = async {
my $t = 0;
$t += log( $_ ) for 230000..565000;
return $t;
};
my $t = 0;
$t += log( $_ ) for 565001..900000;
$t += $thr->join;
printf "%.15f\n", $t;;
printf "Took %.6f\n", time() - $start;
}
__END__
C:\test>junk32
8829606.110849546300000
Took 0.132204
8829606.110849652400000
Took 0.080650
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.
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.