Web Framework Benchmarks
techempower.com
Web Framework Benchmarks
1–10 of 116 posts
Re: Web Framework Benchmarks
#2The Blog post [1] which explains things in details.
Basically they discovered Docker! Given the amount of hype it had for the best 2-3 years I am surprise, Now it is all Kubernetes. ( Or was that a joke I am not getting )
They had new hardware, and I am surprised it was sponsored by Microsoft. They are also using Azure for Cloud. And the hardware is recent and much better represent the common usage. Before it was a Quad Socket CPU platform that I doubt many are using.
I know a lot of these does not represent real world usage. But even if we pick, Full Stack Framework, ORM usage, Realistic implementation, ignoring the erroneous results at the bottom, we still have a gap of 50x difference in Fortune, which is the only results I look at.
I didn't check out why Ruby + Racks were not working. Hanami wasn't working either. So the best results for Ruby were roda & sequel, both framework by Jeremy Evans.
[1]https://www.techempower.com/blog/2018/06/06/framework-benchm...
Re: Web Framework Benchmarks
#3I love these but I've also seen in some of the implementations that I care about a bit of benchmark gaming. That saddens me and I wonder just how much of it is happening in languages and frameworks that I don't follow.
Re: Web Framework Benchmarks
#4I could never explain why mojolicions (Perl) was placed 5th on "Data updates" in Round 14.
Guess that's a think of the past now. (53rd)
Re: Web Framework Benchmarks
#5I wrote the blog entry for this round [1], and I would agree with ksec (elsewhere in these comments) in recommending that readers start there since it includes the highlights of this round. I apologize ahead of time for my humor.
It's still a bit early out here in California, but if anyone has any questions, I will try to answer as I can!
[1] https://www.techempower.com/blog/2018/06/06/framework-benchm...
Re: Web Framework Benchmarks
#6The Blog post [1] which explains things in details. Basically they discovered Docker! Given the amount of hype it had for the best 2-3 years I am surprise, Now it is all Kubernetes. ( Or was that a joke I am not getting ) They had new hardware, and I am surprised it was sponsored by Microsoft. They are also using Azure for Cloud. And the hardware is recent and much better represent the common usage. Before it was a Q…
> ( Or was that a joke I am not getting )
Yes, that was a bit of a joke in the blog entry. We suspected for years Docker would be a good fit for this project. Only within the past months did we find the time necessary to convert the hundreds of test permutations to Docker. It wasn't a quick thing, but we did get into a rhythm. The "joke," for whatever it's worth, is simply that we didn't sufficiently appreciate how useful it would be for this project and how insignificant the overhead would be. Perhaps we would have prioritized it higher in the past had we known. But it's done now!
In brief, the Docker conversion effort has increased the stability and reliability of the results.
There are a huge number of ways to consume the results and as many opinions. We welcome the diverse points of view and hope you find the data useful!
Re: Web Framework Benchmarks
#7I had not checked these for a good long while. (Probably around round 10 or 11.) Looking back in on it now, holy MAN!
C (C++) and Java. Wow.
Even though I'm old, I'd sort of forgotten how speedy they can be. It's strange, because I actually work with Java and C in making streaming game engines. And you kind of get used to thinking in terms of millions on a set of hardware. So you think Java and C are slow. Then you realize if you were using Python or Node or anything other than C or Java really, you'd likely still be working out how to support tens of thousands on that same set of hardware. (If that.)
We can get so used to what we have. Maybe that's just a human thing.
Re: Web Framework Benchmarks
#8I've been following these benchmarks for some time, and am always shocked that Spring does so poorly (it's 7% here). I haven't had any performance issues with Spring in production, so these benchmarks are puzzling. Are the other frameworks really that much faster in practice?
Re: Web Framework Benchmarks
#9Is 'Fortunes' a test involving the quote generating program? Also, is the difference between 'Single Query' and 'Multiple Queries' concurrency? I always look at these but I have trouble understanding the test cases.
Re: Web Framework Benchmarks
#10I love these but I've also seen in some of the implementations that I care about a bit of benchmark gaming. That saddens me and I wonder just how much of it is happening in languages and frameworks that I don't follow.
It's interesting to look at the source code. There's definitely some heavy differences in how each implementation is handling underlying aspects of the tests.
Just looking at the database related ones to see about some of the differences in interesting.
It also doesn't look like the Elixir code has really been updated in about 2 years (aside from version bumps). It's still using a JSON encoder (Poison) that's 4x slower than the primary one (Jason). For multiple queries, Ecto hands back the connection after every query for concurrency sake. Looks like the Plug logger is still setup on the endpoint.
I'd be really interested to see the Discord folks look at that as a pet project. :-)