Can you please add CppCMS (http://cppcms.com/wikipp/en/page/main) and Gwan(http://gwan.com/). Both are high performance web development framework claiming fast.
Web Framework Benchmarks Round 3
21–30 of 30 posts
Re: Web Framework Benchmarks Round 3
#22it's very strange that in the Multiple Query Tests vertx performed very well with EC2 and less well with dedicated hardware (it's position changed drematically), but not so in other tests...
Re: Web Framework Benchmarks Round 3
#23Can you please add CppCMS ( http://cppcms.com/wikipp/en/page/main ) and Gwan( http://gwan.com/ ). Both are high performance web development framework claiming fast.
Hi rjoshi. I've added issues at our Github repository for those two. I don't feel that we're qualified to create the benchmark tests for those two, so it would ideal to receive those as pull requests.
Re: Web Framework Benchmarks Round 3
#24it's very strange that in the Multiple Query Tests vertx performed very well with EC2 and less well with dedicated hardware (it's position changed drematically), but not so in other tests...
Agreed. We only have conjecture on that one. I suspect that something in either the test or the Vert.x code is causing a blocking behavior. If I recall correctly, that test on i7 is not able to fully saturate the CPU cores.
Re: Web Framework Benchmarks Round 3
#25Memory consumption charts would be a great thing to have. (edit: oh, I see: https://github.com/TechEmpower/FrameworkBenchmarks/issues/10...)
Re: Web Framework Benchmarks Round 3
#26Where is all the attention that happened for the first two rounds? (I'm really hoping someone will explain why Go's database results are so slow, and what can be done to improve that.)
The most likely cause is in the mysql driver. Go provides an interface for drivers to implement, similar to how JDBC does in Java. One of the go developers, Brad Fitzpatrick, commented [1] that the actual code used by the benchmark looks OK. The discussion of these test results on golang-nuts [1] triggered a number of performance related pull requests [2] to the mysql driver used. Also of interest: https://code.googl…
Just for the reference: It was not the drivers fault but an bug in the database/sql package, which was fixed in https://code.google.com/p/go/source/detail?r=45c12efb46
Re: Web Framework Benchmarks Round 3
#27This 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-limi…
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.
Actually, tornado's test uses Mongo, which makes the test quite uncomparable to others using MySQL!
https://github.com/TechEmpower/FrameworkBenchmarks/blob/mast...
Re: Web Framework Benchmarks Round 3
#28Earlier quoted context omitted.
The most likely cause is in the mysql driver. Go provides an interface for drivers to implement, similar to how JDBC does in Java. One of the go developers, Brad Fitzpatrick, commented [1] that the actual code used by the benchmark looks OK. The discussion of these test results on golang-nuts [1] triggered a number of performance related pull requests [2] to the mysql driver used. Also of interest: https://code.googl…
Just for the reference: It was not the drivers fault but an bug in the database/sql package, which was fixed in https://code.google.com/p/go/source/detail?r=45c12efb46
Thanks for posting the follow up here, Julien. I'm glad this has been fixed. We look forward to the Round 4 numbers with Go fixed up.
Re: Web Framework Benchmarks Round 3
#29Sure wish you'd benchmark the Perl Frameworks.. without them, the list is just incomplete and discriminatory..
Re: Web Framework Benchmarks Round 3
#30Sure wish you'd benchmark the Perl Frameworks.. without them, the list is just incomplete and discriminatory..
We have not discriminated on pull requests, except where a proposed test is redundant (say, testing the same framework as an existing test but with a minor tweak) or doesn't work for us (we can't get the test to run).
Others from the Perl community submitted pull requests for some Perl framework subsequent to Round 3 and we will be including them going forward.
Look to see that data included soon!