Comments on: ErlyWeb vs. Ruby on Rails EC2 Performance Showdown

By: motek

motek — Wed, 26 Mar 2008 15:04:20 +0000

Try ruby 1.9 (compiled from source not from repository) and rails 2 :)

By: zed

zed — Thu, 14 Feb 2008 23:14:45 +0000

and a would like to see ruby 1.9 in comparison
it was released last christmas and ist 5-10 times faster than 1.8

By: zed

zed — Thu, 14 Feb 2008 23:03:27 +0000

you could use Thin or at least evented mongrel instead of mongrel to boost the rails app
but rails is known as the slowest Ruby Webframework around so who cares

By: Richard

Richard — Fri, 14 Dec 2007 18:56:00 +0000

I’ve been reading the EC2 doc and I’m clueless as to how one would install a yaws/erlyweb server and more importantly how much would such a server cost to run? Just because the WS was open, does not mean it’s running… where is the line drawn?

By: Comet Daily » Blog Archive » Getting started with Comet on Erlang

Comet Daily » Blog Archive » Getting started with Comet on Erlang — Fri, 14 Dec 2007 08:05:45 +0000

[...] ErlyWeb, a MVC web framework tailored to yaws and six times faster than RubyOnRails, according to a benchmark done by Yariv Sadan, the author of the framework. If you are considering adapting yaws for Comet, [...]

By: jey

jey — Thu, 13 Dec 2007 09:54:05 +0000

mmh.. ok for Rails but… what the hell is ErlyWeb?!

By: Yariv

Yariv — Thu, 13 Dec 2007 01:33:48 +0000

JFred, I don’t think it’s a big issue that the text is static. I just wanted to make sure that the app does at least some computation before returning. I don’t want to waste too much time tweaking this code where there isn’t likely to be a big impact on performance.

By: JFred

JFred — Tue, 11 Dec 2007 17:38:23 +0000

Um, with the closing bracket:
].map{|x| “” + x + “\n”}

By: JFred

JFred — Tue, 11 Dec 2007 17:36:39 +0000

Your blog software mangled my code. Should I have used pre?

Let’s try this line:
.map{|x| “” + x + “\n”}

By: JFred

JFred — Tue, 11 Dec 2007 17:31:47 +0000

I actually have some similar code in a rails app I made. I computed the insides of the table into a class variable (inside the class but outside any method) essentially like this:

@@redLines = ["text..", "lines of text", ...
].map{|x| “” + x + “\n”}

def initialize
@redLines = @@redLines # copy ref so view can see it.
end

In other words, I removed the loop from the view since the text was constant. Do that for Rails and Erlang too and see what happens.

Alternatively, compute the text more dynamically with variation on each run to defeat caching. But constant text in an instance method is a contradiction.

Come to think of it, it might be that the performance difference is due to differences in default cache configurations. With constant text.