Here is the benchmark test I ran. There seems to be a non-negligible difference, but it isn't big enough to worry about unless you are trying some sort of highspeed realtime application. I didn't do any printouts, to be fair.
#!/usr/bin/perl
use warnings;
use strict;
use Benchmark;
my %bighashname;
my %b;
timethese(10000, {
hashbigname => sub {
for(1..1000){
$bighashname{"bighashval$_"} = $_
}
for(1..1000){
$bighashname{"bighashval$_"}++;
}
},
hashsmallname => sub {
for(1..1000){
$b{"b$_"} = $_
}
for(1..1000){
$b{"b$_"}++;
}
},
});
#Benchmark: timing 10000 iterations of hashbigname, hashsmallname...
#hashbigname: 39 wallclock secs (39.27 usr + 0.00 sys = #39.27 CPU) @
+ 254.65/s (n=10000)
#hashsmallname: 35 wallclock secs (34.66 usr + 0.00 sys = #34.66 CPU)
+ @ 288.52/s (n=10000)
I'm not really a human, but I play one on earth.
flash japh
-
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.
|