It's a useful data point to know the speed of frameworks, but what matters most to me is speed of development and whether or not I enjoy the process.
Wish there was a way to benchmark those points.
Web Framework Benchmarks Round 2
61–70 of 241 posts
Re: Web Framework Benchmarks Round 2
#62As an amateur hacker and after 275 days of reading Hacker News I feel I can now navigate in the sea of client side Javascript frameworks. With the introduction of this data on web framework performance, I now have another set of choices that I am completely unqualified to comprehend. My first impression is that this data shows about 3 levels of web frameworks. At the bottom (slowest) we have Django's and Rails and ma…
In general, I echo ConstantineXVI's comment. However, I'm also curious to know where the definite line is between the bottom half and the top 5 on the table. At what point does a team go "We're getting hammered and our backend is the problem. We have to switch to X or Y because our API on Z has reached its limit."
Re: Web Framework Benchmarks Round 2
#63Earlier quoted context omitted.
We've had a lot of requests Mono, and are actually very interested in trying this out. We've been hesitant to move forward only because we're unsure how stable the C# community believes Mono to be. We hope to have that test at some point though, but the fastest way to get a test included is to issue a pull request. So if anyone is interested in trying this out, let us know and we can help guide the process.
Cool, a note on the stability side: http://www.servicestack.net and the live demos http://www.servicestack.net/#livedemos have always been hosted on Linux/Mono in all the years it's been in existence. Is GitHub issues the best way to ask for guidance?
Yes, Github issues is a good place to ask for guidance.
Re: Web Framework Benchmarks Round 2
#64migth be interesting to add Erlang.
We have at least one Erlang test that came in yesterday and will be included in the next round of benchmarks.
Re: Web Framework Benchmarks Round 2
#65As an amateur hacker and after 275 days of reading Hacker News I feel I can now navigate in the sea of client side Javascript frameworks. With the introduction of this data on web framework performance, I now have another set of choices that I am completely unqualified to comprehend. My first impression is that this data shows about 3 levels of web frameworks. At the bottom (slowest) we have Django's and Rails and ma…
Netty, gemini and servlet are all java server solutions without a thick framework layer getting in-between. What you can tell from these benchmarks in my opinion is that java (or rather the JVM) has the best "raw" performance. Frameworks introduce a slow-down factor on top of the raw platform, and different frameworks have different slow-down factors.
You have to trade off developer productivity for performance when it comes to choosing frameworks. The slower the framework the more it does for you.
Re: Web Framework Benchmarks Round 2
#66This is great stuff. I'd love to see some more frameworks written in compiled native languages like Haskell and C!
Re: Web Framework Benchmarks Round 2
#67Any thoughts of putting some Erlang in there?
We got a pull request for an Erlang framework (my brain is not letting me pull up the name) yesterday that we accepted, but sadly it was too late for this round of benchmarks. We will include it in the next round.
Re: Web Framework Benchmarks Round 2
#68Yesod disappoints! Unfortunate for how much it is hyped. This is definitely good to know, even if it appears that the Warp server was not used.
Re: Web Framework Benchmarks Round 2
#69It's a useful data point to know the speed of frameworks, but what matters most to me is speed of development and whether or not I enjoy the process. Wish there was a way to benchmark those points.
I 100% agree with this. It has been a huge point of discussion for us here internally. "Developer efficiently with language x." Ultimately, language performance does matter but there are ways to make up for less performant languages. If it takes you 2x as long to get something out the door though, then that is a huge problem.
Just use the language and framework you are most efficient in and enjoy using. Worry about framework performance when you notice server load increasing over time.
Re: Web Framework Benchmarks Round 2
#70I think I said something similar on the first round, but for the Python tests, I'd be curious to see alternate runtimes and/or concurrency strategies: pypy, gevent, and probably the confluence of the two (though it requires quite a bit more hacking, since gevent doesn't officially support pypy).