You have file size as the key to your hash so sort just needs to be: 

for my $key( sort { $b <=> $a } keys %sizehash ) {
    # blah
}

[download]

HOWEVER -> From the practical point of view your data structure is ass about. You really want the full path as the key (unique) not the file size (not unique). For example if you have two files of 1,000,001 bytes then only the second one you find will be seen as it will overwite the filename stored with the 1,000,001 byte key.

To sort a hash numerically by value once you fix the BUG you would do: 

for my $file( sort { $sizehash{$b} <=> $sizehash{$a} } keys %sizehash 
+) {
    my $size = commas($sizehash{$file});
  last if $y++ > 10;
    print "$size: $file\n";
}

[download]

cheers

tachyon

In reply to Re: finding top 10 largest files by tachyon
in thread finding top 10 largest files by bfdi533

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.