Christian888:

I haven't analyzed your code in any depth (time constraints, lack of sleep, too many interactions with global variables). But it does appear that you're not taking advantage of some of the advantages of perl to get things going a bit faster.

A couple random notes:

• Upon a cursory review, it appears like you do quite a few unnecessary array copies. It may help if you try passing them around by reference instead of by value. For example:
  

  $population = regenrate_population();
  ...
  sub regenrate_population {
      my $new_population = [];
      for my $i ( 0 .. ( $population_size - 1 ) ) {
          my $chromosome1 = get_nonrandom_chromosome();
          my $chromosome2 = get_nonrandom_chromosome();
          $$new_population[$i] = get_child( $chromosome1, $chromosome2 )
  +;
      }
      return $new_population;
  }
  [download]

• You do a bunch of looping instead of taking advantage of list operations, like array slices. Consider the difference between:
  

  my $crossover_point = int( rand($chromosome_size) );
  for my $i ( 0 .. ( $chromosome_size - 1 ) ) {
      if ( $i < $crossover_point ) {
          push( @$new_chromosome, @$chromosome1[$i] );
      }
      else {
          push( @$new_chromosome, @$chromosome2[$i] );
      }
  }
  [download]

  and:
  

  my $crossover_point = int( rand($chromosome_size) );
  $new_chromosome = [
       @{$chromosome1}[ 0 .. $crossover_point-1],
       @{$chromosome2}[ $crossover_point .. $#{$chromosome2} ] 
  ];
  [download]

• You can take advantage of the malleability of perls data structures to prevent recalculations, too, but I'm having trouble thinking of a good way to say it. I'll try again in the morning, if time allows. (Short form: rather than store population as a list of scalars (chromosomes), store the population as a list of array references, [ chromosome, fitness score, etc ]. Then when you call get_population_fitness_score, you can populate the fitness score slot, and not recompute it again until the next pass.
• I don't know that anyone claims that perl is all that fast, anyway. We don't use it because the final product is all that fast, but because it lets us get the final product quickly. That said, I rarely find the speed of the final product to be noticeable for my purposes.
• Finally, if you're concerned about speed, then you should definitely start playing with Benchmark so you can tell the difference in speed between various code constructs, and with a profiler so you can find out which bits of your program are consuming all the time. (I think it's Devel::Profile, but I'm not certain, as I rarely profile my code.)

...roboticus

When your only tool is a hammer, all problems look like your thumb.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.