Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
ErlyWeb vs. Ruby on Rails EC2 Performance Showdown (yarivsblog.com)
13 points by BitGeek on Dec 10, 2007 | hide | past | favorite | 11 comments


The last commenter on the original thread is absolutely right: Rails follows different "concurrency model", i.e. it needs multiple processes to run well, especially on multi-core CPUs. He needs to create a cluster of 4-6 mongrels on 2-core CPU and the margin will shrink.


This is the next thing I'll test.


... and? Rails forks. It's slow even for a Ruby framework. You could beat both ErlyWeb and Rails handily in C, if your priorities were that far out of whack. Nobody uses Rails for its speed.


It's just about speed as much as how much abuse your server can take before it stops serving.


Servers is absolutely the LAST thing you should worry about today. They cost next to nothing when you compare their cost to the cost of development.

If you need more performance out of Rails, create another VPS and add the mongrels to a cluster. Problem solved.


EC2 instances are virtualized machines, right? What about differing CPU contention (i.e. steal times) based on the load of other virtual machines on the same box?

I don't think the results would change much, but to be safe, I think you should run this comparison on multiple random ec2 instances, to account for differing external loads.


Interesting, my comments about Rails, ERlyweb and WebObjects were deleted, and my title was re-written.


The comment is always lost if you also submit an URL.


The author compiled ErlyWeb and YAWS with HiPE (http://www.it.uu.se/research/group/hipe). Are there any issues with using HiPE instead of the Erlang/OTP compiler?


I will try running the test after recompiling without HiPE and see what difference it makes.


Any idea how they compare when using rails caching? Is there an equivalent in ErlyWeb?

I'd be curious to see the numbers, as the gap could go either way. I'm not sure if rails is worse with threads or worse with rendering or both.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: