Comments on: Rails vs. Ramaze Performance Comparison

By: Ramblings Ramaze vs. Padrino Benchmarks

Ramblings Ramaze vs. Padrino Benchmarks — Sat, 01 May 2010 19:19:36 +0000

[...] in Ramaze since January 2009 when I switched from Rails to Ramaze. At that time, I did some benchmark comparisons. The other day, I heard about Padrino, the micro-framework for Sinatra, which is comparable to the [...]

By: Michael

Michael — Sun, 01 Mar 2009 17:29:14 +0000

@rony: That is curious, indeed. I have been half suspecting Passenger isn’t quite ready for 1.9.1 performance-wise. I think I will run some basic tests without Apache/Passenger and post a follow up article with results.

By: Rony

Rony — Sat, 28 Feb 2009 18:20:16 +0000

I don’t understand these results. If I use this start.rb I get 177 requests per second with 1.8.7 and 313 requests per second with 1.91. This make 1.91 75% faster than 1.8.7. This is consistant with other tests I have run.

require ‘rubygems’
require ‘ramaze’

# Add directory start.rb is in to th e load path, so you can run the app from
# any other working path
$LOAD_PATH.unshift(__DIR__)

# Initialize controllers and models
require ‘controller/init’
require ‘model/init’

Ramaze::Global.sourcereload = false
Ramaze::Global.sessions = false
Ramaze::Log.ignored_tags = [:debug, :info]

Ramaze.start :adapter => :thin , :port => 7000

By: Michael

Michael — Fri, 20 Feb 2009 01:21:48 +0000

@AJ: I do like Merb and have played with it quite a bit. Before writing this article, I was actually benchmarking Merb vs. Rails and it did show very good performance differences. However, my thinking is that if Merb is becoming Rails 3.0, I don’t need to learn Merb at this juncture. I can simply choose Rails 2.2.2 now and build with expectation of reaping the benefits of Merb when Rails 3.0 comes around. This strikes me as a cleaner “upgrade path” than to switch to Merb now then migrate back to Rails when 3.0 is out.

By: AJ

AJ — Thu, 19 Feb 2009 21:12:34 +0000

Does Merb not achieve what you want? We’ve been using it at the core of Chef’s (http://github.com/opscode/chef/tree/master) server component without issue, the performance is outstanding and interacted cleanly with CouchDB