The following is my fun spin using dualvar, based on choroba.pl. I tried minimizing memory consumption by using one hash and one array. The memory consumption is similar to llil.pl and performance slightly faster than choroba.pl.
See also, parallel solution update.
#!/usr/bin/perl
use warnings;
use strict;
use feature qw{ say };
use Scalar::Util qw{ dualvar };
warn "start\n";
my $tstart1 = time;
our (%by_word, @data);
while (<>) {
chomp;
my ($k, $v) = split /\t/, $_;
$by_word{$k} += $v;
}
my $tend1 = time;
warn "get properties: ", $tend1 - $tstart1, " secs\n";
my $tstart2 = time;
while (my ($k, $v) = each %by_word) {
push @data, dualvar($v, $k);
}
# output array of dualvars; sorted by number desc, string asc
say "$_\t".(0+$_) for sort { $b <=> $a } sort { $a cmp $b } @data;
my $tend2 = time;
warn "sort + output: ", $tend2 - $tstart2, " secs\n";
warn "total: ", $tend2 - $tstart1, " secs\n";
-
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.