Reputation: 134601
I'm looking for real life benchmarks comparing web frameworks based on dynamic languages (Python, Ruby, Groovy and Lua). Even better if they're compared up against classic solutions based on PHP, Java, ASP.NET maybe even Perl. I'm particularly interested in:
EDIT: As for Sean's answer:
Let me quote book "Struts2 in Action" by D. Brown, C.M. Davis and S. Stanlick:
"If you want, you could roll your own framework. This is actually not a bad plan. It assumes a couple of things though. First, you have lots of really smart developers. Two, they have the time and money to spend on a big project that might seem off topic from the perspective of the business requirements. Even if you have the rare trinity of really smart people, time and money, there are still some drawbacks. I've done work for a company whose product is built on an in-house framework. The framework is not bad. But a couple of glaring points can't be overlooked. First, new developers will always have to learn the framework from the ground up. If you are using a mainstream framework, there’s a trained work force waiting for you to hire them. Second, the in-house framework is unlikely to see elegant revisions that keep up with the pace of industry. In fact, in-house frameworks seem to be suspect to architectural erosion as the years pass and too many extensions are less elegantly tacked on than one would hope."
I couldn't agree more.
Upvotes: 1
Views: 4498
Reputation: 387
Techempower benchmark:
http://www.techempower.com/benchmarks
They are comparing a lot of frameworks and accept new frameworks for comparison. Interface very intuitive. In my view, it is the best benchmark now.
World wide wait - 1 hour speech
http://www.parleys.com/#id=2942&st=5
Django is not here, it's only benchmark of JVM frameworks. But still, it is quite scientific, worth it.
Upvotes: 2
Reputation: 6507
If your project has a serious, identifiable, need for speed, to the point where your framework is a consideration, taking a general-purpose framework is a bad idea to begin with. They're all going to be too slow, by virtue of being high-level, general purpose & extensible.
If your project does not have a hard requirement for an ultra-efficient framework, then you probably wasted more time typing in the question than you'd actually save by going with the 'fastest' framework.
Upvotes: 17