comment on

Fully agree with eliminating the multiple call to keys.

I'm also a big believer in reducing nested hash references. For the small price of assigning another variable, you can eliminate the cost of several steps of hash key lookups, and improve readability as a bonus.

my $temp;
while (($entry,$temp) = each %my_hash) { 
  foreach $timeStamp ( sort keys %$temp) {

    my $hash_ref = $temp->{$timeStamp};

    my @tskeys = sort keys %$hash_ref;
    print $Hentry "$entry\t$timeStamp\t", scalar @tskeys;
    print $Hentry "\t$_\t", $hash_ref->{$_} for @tskeys;
    print $Hentry "\n";
  }
}
[download]

In reply to Re^2: Optimizing Iterating over a giant hash by ruzam
in thread Optimizing Iterating over a giant hash by oron

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.


Perl Monk, Perl Meditation
	PerlMonks