From: Jeremy Henty <jeremy@...>
Date: 2006-07-15T07:25:23+09:00
Subject: Re: How to speed up ruby and make it as fast as possible

On 2006-07-14, Simon Kr�ger <SimonKroeger@gmx.de> wrote:

> +1
>
> I don't get why Jamal is called a troll here.
>
> [...]
>
> The original Poster was asking very specific things like
> configurations, resources, memory limits, priorities and got
>
> "Write it C."
>
> as an answer. I would consider that trolling, and jamal seems to
> think so too.

irb$ parent.value += 1

I too am somewhat disappointed by this thread.  People, we do *not*
need to be reminded that Ruby is slower than C .  We *would* benefit
from serious discussion of how (or if) Ruby could be faster.  Will
YARV do this?  (The last time I saw any YARV benchmarks it performed
more slowly than Ruby 1.x on some tests.  Has this changed?  Will it
change?)  Is there anything besides YARV that promises to address
performance or is YARV the only horse in the race?  If I am
considering rewriting my Ruby in C for performance reasons, how can I
decide whether it is worth waiting for for YARV?

These are sensible questions.  They deserve sensible answers.  They
aren't getting them (not on this thread at any rate).

Lest I be accused of throwing stones from inside a glass house, let me
add a few links:

ruby-prof: <URL:http://ruby-prof.rubyforge.org/>
Polishing Ruby: Space vs Time: <URL:http://blog.zenspider.com/archives/2005/04/space_vs_time.html>
Zed on Ruby, Rails, Mongrel, and More: <URL:http://www.oreillynet.com/ruby/blog/2006/05/post.html>
  "I'll be honest right away though and say that Ruby is slow. The
   Ruby community has been ignoring the huge "performance" elephant
   standing in the room and they need to start talking about it so it
   goes away."

Regards, 

Jeremy Henty