4 ms·
The play test was written totally incorrectly since it used blocking database calls. Since play is really just a layer on top of Netty it should perform nearly
by jholla14 14y ago
The play test was written totally incorrectly since it used blocking database calls. Since play is really just a layer on top of Netty it should perform nearly as well if correctly written.
- goodwink 14y agoI believe they're encouraging pull requests to fix that sort of thing. It will be interesting to see if it helps to that degree; I hope so!
- abalone 14y agoBut Play's trivial JSON test was much slower than Netty's.
- mrspeaker 14y agoThat's because they inexplicably use the Jackson library for the simple test, rather than Play's built in JSON support (they use the built-in JSON for the other benchmarks).
- rzidane 14y agoBoth Netty and Play use Jackson though one the Netty version uses a single ObjectMapper and the Play version uses a new ObjectNode per request (created through Play's Json library).
- ms-tg 14y agoI hope this gets fixed!
- abalone 14y agoNo, they use Play's JSON lib. It's kind of a moot point because Play's lib is in fact a wrapper for Jackson. Here's the source: https://github.com/TechEmpower/FrameworkBenchmarks/blob/master/play-java/app/controllers/Application.java https://github.com/TechEmpower/FrameworkBenchmarks/blob/mast... So the question stands: If Play & Netty are using the same JSON serialization code, why is Play seven times slower?