The Play JSON controller is using Futures to do JSON serialization.
https://github.com/TechEmpower/FrameworkBenchmarks/blob/mast...
Compare this to the Java Servlet, which just serializes directly in the Servlet callback.
https://github.com/TechEmpower/FrameworkBenchmarks/blob/mast...
The former seems like overkill.
Re:Web Framework Benchmarks Round 2
by redtuesday on Friday April 05, 2013 @01:36PM
(#5499809)
This is not the version which was used in the tests. The tests used a earlier version.
Regarding Lift: good news, we received a pull request for that earlier this week. Too late for this week's run, but we'll try to get it in next week!
Re:Web Framework Benchmarks Round 2
by bsnyder788 on Friday April 05, 2013 @01:20PM
(#5499697)
My best guess is that the java one is slow due to ebean (I've always seen huge performance improvements from switching to raw jdbc). The scala one I have no clue.
Re:Web Framework Benchmarks Round 2
by redtuesday on Friday April 05, 2013 @01:40PM
(#5499839)
More likely because the version uses only as many threads as the cpu has cores. Whereas the servlet version for example has 128 thanks to the default resin configuration.
Re:Web Framework Benchmarks Round 2
by bsnyder788 on Friday April 05, 2013 @01:59PM
(#5499952)
That would definitely be an issue as well. Although, this is easily configurable within the application.conf file if I remember correctly.
I'd like to see Lift in there if you guys do another round.