Note that there are some explanatory texts on larger screens.

plurals
  1. POWeb frameworks performance comparison
    primarykey
    data
    text
    <p>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:</p> <ul> <li>Django</li> <li>Ruby on Rails</li> <li>Grails</li> <li>Zend Framework</li> <li>Struts2</li> </ul> <p>EDIT: As for Sean's answer:</p> <ol> <li>It's more hypothetical question, in real life I've gotta choose based on more constrains then just raw speed.</li> <li>Speed is not the only, and not even the most important parameter to take in account. It's actually more interesting how these frameworks <strong>scale</strong>.</li> <li>Using standard, well know framework have advantages, that in most cases <em>(unless you're doing something like EVE on-line)</em> out-weight raw speed improvement. </li> </ol> <p>Let me quote book <a href="http://www.manning.com/dbrown/" rel="nofollow noreferrer">"Struts2 in Action"</a> by D. Brown, C.M. Davis and S. Stanlick:</p> <p><em>"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."</em></p> <p>I couldn't agree more.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload