From: Andreas Schwarz <usenet@...>
Date: 2004-06-21T08:18:14+09:00
Subject: Re: rubys web performance

Florian Weber wrote:
>> Where's the problem? You have to load the files only once, so it 
>> doesn't
>> matter how long it takes to parse them. CGI is no use for "real"
>> applications, use fastcgi, webrick or mod_ruby.
> 
> well, but i think thats exactly the point why ruby is really hard to use
> for general web stuff..
> 
> there are barely any hosters who support fastcgi, webrick or mod_ruby.
> especially since the last one is not usable for shared hosting. so you
> have to rely on cgi..

I agree, ruby support on shared servers is poor. This is one of the
reasons why I'm using a virtual server from www.vdserver.de.

> and anyways, why does it take ruby so long to load the files and compile
> it when the same would only take a fragment of it with php?

Did you really try PHP CGI with source files of comparable size (don't
forget that every file you require could itself require other files)?

I don't know exactly how the parsing mechanism in PHP and Ruby differs,
and I don't know if there is actually a difference in performance; but
I wouldn't be surprised if PHP was faster, because the language is
*much* simpler to parse than Ruby. However, I don't think it's really a
problem.