That Perl smells a little like Java.

For example, for some of those smaller functions, I'd do this: 

sub gene_length {
    my @gls = sort map { length } keys %genome;
    die "Invalid genotype" unless $gls[0] == $gls[$#gls];
    return $gls[0];
}

[download]

And this: 

use List::Util 'first';
sub check_for_winner {
    return first { get_result($_) == $target } @population
}

[download]

And this; 

use List::Util 'sum';
sub get_population_fitness_score {
    return sum map { get_fitness_score($_) } @population;
}

[download]

(Or just inline those statements, if they're only used once.)

In other words, when you can trim it down so that you can actually tell what it's doing at a glance, then it's easier to benchmark!.

In reply to Re: Perl slower than java by Anonymous Monk
in thread Perl slower than java by Christian888

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.