Let me state once again that the Rails benchmarks are absolutely way off. Snap would still be faster - much faster - but you can expect several thousands req/s from that Rails app on that kind of hardware.
I did my own testing, but I didn't publish them because I left Haskell completely unoptimized and didn't really have the time to try to optimize it. I also added play (http://www.playframework.org) into the mix, because I admire the framework and how closely it mimics Rails, but in Java (and Scala).
Still, I saved 'em, so here you go:
On a 2.27Ghz Xeon dual quad core with 12 GB ram, using Snap's tests from GitHub:
Note, Snap had a mem leak when performing the file test that caused a machine with 12 GB to swap, but that may be because I used the Ubuntu Lucid version of Haskell.
Also note, Play is damned fast. And relative to other Rails options, JRuby with glassfish is as well.
Although these seem like useful (and impressive) baseline benchmarks, won't the really important benchmarks come from measuring actual dynamic content generation, and/or caching performance for generated dynamic content?
When I did experiments with RoR versus Haskell via FCGI, Haskell had around a two orders of magnitude performance advantage under load and only required a single OS process.
[+] [-] acangiano|16 years ago|reply
[+] [-] rufugee|16 years ago|reply
Still, I saved 'em, so here you go:
On a 2.27Ghz Xeon dual quad core with 12 GB ram, using Snap's tests from GitHub:
The full results are here:Pong: http://gist.github.com/414724 File: http://gist.github.com/414728
Note, Snap had a mem leak when performing the file test that caused a machine with 12 GB to swap, but that may be because I used the Ubuntu Lucid version of Haskell.
Also note, Play is damned fast. And relative to other Rails options, JRuby with glassfish is as well.
[+] [-] wwortiz|16 years ago|reply
Edit: Oh he responded to you the last time, but I'll leave this here so others can see
[+] [-] rubyrescue|16 years ago|reply
[+] [-] angusgr|16 years ago|reply
[+] [-] prb|16 years ago|reply
[+] [-] warfangle|16 years ago|reply
[+] [-] matthijs|16 years ago|reply
[+] [-] JimBastard|16 years ago|reply
[deleted]