From: Roger Pack <rogerpack2005@...>
Date: 2007-09-28T00:40:49+09:00
Subject: Re: question on bottleneck of ruby

Thanks Kirk.

Follow-up question: it seems like there have been a lot of 'replacement 
attempts' of the Ruby interpreter, but none of them seem to have really 
really sped it up (jruby, rubinius, etc.) They do add cool features like 
thread safeness or what not, and in certain instances are faster, but 
not like 'we've overcome the bottleneck!' faster.
Does this mean that they suffer from the same bottlenecks?  Is Ruby just 
a hard language to optimize for?  Do they all tree walk and have slow 
method dispatch and a slow GC or something?  Hmm.

Stay well.
-Roger
>> So my question is...where is the bottleneck?  Is it in method lookup?
> The dynamic nature of the method dispatch.  The overall implementation 
> --
> both the tree walker versus a vm, and some of the implementation 
> details.
> The GC can also be a bottle neck.  It stops the world when it runs, and 
> it
> has to touch every object when it runs, so as the program gets bigger 
> (in
> object count), the GC burden gets higher.
> 
-- 
Posted via http://www.ruby-forum.com/.