The first one you wrote was the fastest:
Benchmark: timing 1000000 iterations of tin1, tin2, tin3...
tin1: 1 wallclock secs ( 0.59 usr + 0.00 sys = 0.59 CPU) @ 16
+86340.64/s (n=1000000)
tin2: 1 wallclock secs ( 0.75 usr + 0.00 sys = 0.75 CPU) @ 13
+33333.33/s (n=1000000)
tin3: 3 wallclock secs ( 2.22 usr + 0.00 sys = 2.22 CPU) @ 45
+0450.45/s (n=1000000)
Rate tin3 tin2 tin1
tin3 450450/s -- -66% -73%
tin2 1333333/s 196% -- -21%
tin1 1686341/s 274% 26% --
the input to get this was:
$results = timethese(1000000,{
tin1 => '$output[int($_/3)] += $arr[$_] for 0..@arr-1;',
tin2 =>'$out[$_] = ($arr[(3*$_)]+$arr[(3*$_+1)]+$arr[(3*$_+2)]) for 0.
+.(scalar(@arr)/3 - 1);',
tin3=>'for (0..$k) {
$output[$_] = $arr[$b] + $arr[$b+1] + $arr[$b +2];
$b += 3;
}
'});
Benchmark::cmpthese( $results );
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|