RoR, Django, TurboGears, Symfony etc Framework Speed Tests
Alrond has put up a great little speed test comparison between a few different frameworks with very interesting results. I’ll have to say that from these tests Django is totally whopping some ass. In every area; CPU, Memory and Requests Per Second.
Rails didn’t fair TOO bad relatively speaking. But its interesting how frameworks can differ in performance. For example, Django comes out on top by 200-300% in some cases, Rails and Turbo gears comes out in a 2nd place tie. But TurboGears and Django are both written in Python yet Django is rocking TurboGears’ and Rails’ socks by 200-300%.
I am though from these tests disappointed in the performance between Rails 1.2.1 and 1.1.6 (Especially since we just upgrade SugarStats to 1.2.1…). It seems to be specifically to errors/changes between 1.1.6 and 1.2.1, but in some of his tests Rails 1.1.6 beat it out by a good margin.
Take a look for yourself: The performance test of 6 leading frameworks
.
Posted on January 30, 2007
Filed Under Analytics, Art & Design, CSS/XHTML, Daily Thoughts, Design, Entertainment, General, Hardware, Hosting, PHP/MySQL, Quotes, Ranting, Ruby on Rails, Security, Tech, Web
Related Posts:
-
In-Depth Ruby on Rails and Django Comparison
CakePHP: RoR-like PHP framework
Ruby on Rails 1.1 Released!
Speed up Safari
Random Rhetoric for 2007-09-07
New Upgrade: 20Mbit Wanadoo ADSL
Comments
3 Responses to “RoR, Django, TurboGears, Symfony etc Framework Speed Tests”
Leave a Reply

Wow. Those are impressive test results, and very surprising.
I was kind of hoping to see Rails knock everything over.
I’m glad to see that he provided all of his test setup for everyone to look at it. Everything seems fair to me.
I wish he had tested Seaside, though.
Hey Michael,
Yeah, I’m always hoping that for Rails too haha
Kinda depressing to see these results but then I remember how much I enjoy Ruby and how it works just fine for what I need.
Yeah, seaside would have been cool. I’m starting to read up a bit on it.
Take a look again! http://www.alrond.com/en/2007/feb/04/in-addition-to-the-test-of-mvc-frameworks/
He had Rails 1.2.1 configured wrong at first, which made it’s results lower than it should have been.