From: Robert Klemme <shortcutter@...>
Date: 2010-10-07T21:12:31+09:00
Subject: Re: A Real World example for Ruby to "compiled" version discussion

On Thu, Oct 7, 2010 at 2:57 AM, Ryan Davis <ryand-ruby@zenspider.com> wrote:
>
> On Oct 6, 2010, at 09:55 , Philip Rhoades wrote:
>
>> The main problem I see with some of the Ruby conversions that I have looked at (eg RubyInline) is that the performance problem comes in in repeating the WHOLE simulation with different starting parameters which is done thousands of times - so it is not like you have a single recursive algorithm which is a bottleneck that can be optimised or rewritten in C or something.  There are lots of little steps that happen millions of times . .
>
> Could you expand on this??

Specifically

- What properties (conceptually) does an individual / a population have?

- What calculations are done for each individual / population?

- What kind of iteration is applied?

Kind regards

robert

-- 
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/