[bhauer]

This is the latest update to our benchmarking of web application frameworks and platforms. Since Round 2, we've had several pull requests. There is more Scala, Erlang, Lua, PHP, Java, Haskell, more everything! (Sorry, we've not yet received .NET/Mono pull requests.)

Additionally, with the help of the author of Wrk, we've been able to change the methodology to use time-limited tests (1 minute) rather than request-limited tests (100,000 requests). This means all frameworks are exercised for the same amount of time.

We've migrated the results to a stand-alone site so we have a little more screen real-estate for the charts and tables.

I look forward to any feedback, comments, questions, or criticism. Thanks!

[nobodysfool]

I know all languages are using mysql, but mysql drivers are pretty poor for languages such as 'go' and 'python'. So it does make it quite unbalanced. I'd love to see this with Postgres.

[lbolla]

Actually, tornado's test uses Mongo, which makes the test quite uncomparable to others using MySQL! https://github.com/TechEmpower/FrameworkBenchmarks/blob/mast...

[bhauer]

I agree. We do plan to add Postgres tests in the future. I don't have an ETA for that, however.

[Prathik]

what is meant by raw as in php-raw vs php

[bhauer]

For most of the tests, we expect that an ORM or something ORM-like is used to work with the database. For example, the Ruby tests use ActiveRecord and many of the Java tests use Hibernate. We believe the use of an ORM to be conventional for most production sites.

The "raw" suffix indicates that an ORM is not used. This can give you an idea of the cost of using an ORM (or, in some cases, the cost of having more framework code in general).

The "servlet-raw" test uses raw JDBC to connect to and query the database. The "php-raw" test uses PHP's raw MySQL connectivity and no ORM. The "php" test with no "raw" suffix is using PHP ActiveRecord.