Live data from Hacker News

Web Framework Benchmarks Round 4

techempower.com

61–70 of 358 posts

Re: Web Framework Benchmarks Round 4

#61

For those new to these benchmarks, all of the source code is up on github: https://github.com/TechEmpower/FrameworkBenchmarks We welcome all pull requests, suggestions and criticisms.

Any chance you could add JEE6? The two major JSF 2.1 implementations MyFaces and Mojarra are both missing. I don't expect awesome performance numbers, but since JSF2.1 is the 'official' (sigh) web framework of JEE6, it would be interesting how awful they are compared to some of these other languages. I guess though if this is only testing JSON serialization, it may not make sense. Perhaps adding JAX-RS implementation…

The latest test that we have, dubbed "Fortunes", does server-side templating, so we (or a generous community member) could add a JSF implementation for that test.

Re: Web Framework Benchmarks Round 4

#63
post #36

Off all the top performers, Go seems to be the only sane choice to write a web app. Moreover it is at the sweet spot; expressive, flexible, simple, super performant, good community etc. I think it is convincing enough for me to give Go a serious look for our new app.

As someone who is also really enjoying Go, I think you need to add a huge, gigantic disclaimer before making a statement like this: Go's ecosystem of web development packages is in its infancy. You're not going to find any super-well-documented, super mature/stable web frameworks (thought a few are showing great promise). and some of the individual components (for example, Gorilla) are looking very good, but still have some more cooking to do.

I love the language, but let's not get too carried away until the ecosystem grows. The reality is, if you're going to use Go for web dev, you're going to need to be prepared to do a whole lot of things on your own.

Re: Web Framework Benchmarks Round 4

#65
post #57

Whenever I hear "Java" I also get association "slow". But looking into this list - java web frameworks doing incredible job!

I always assumed the slowness is associated with build times and such. You are slow developing a Java web app, but not running it.

Re: Web Framework Benchmarks Round 4

#66
post #36

Off all the top performers, Go seems to be the only sane choice to write a web app. Moreover it is at the sweet spot; expressive, flexible, simple, super performant, good community etc. I think it is convincing enough for me to give Go a serious look for our new app.

How is go a sane choice and scala isn't?

Re: Web Framework Benchmarks Round 4

#67
post #36

Off all the top performers, Go seems to be the only sane choice to write a web app. Moreover it is at the sweet spot; expressive, flexible, simple, super performant, good community etc. I think it is convincing enough for me to give Go a serious look for our new app.

I take it you didn't switch the graphs to the latency view.

Re: Web Framework Benchmarks Round 4

#68
post #14

Wow, I should really give Go a try.

Agreed, but the language is sufficiently (edit) MORE verbose than Python that it is still a valid strategy to write in Python first, and then rewrite in Go for performance..

It translates fairly directly as well, even with the differences in OO and multi-processing/threading.

Re: Web Framework Benchmarks Round 4

#69

I really don't like these benchmarks. Its like benchmarking Fizzbuzz or something. Frameworks don't do anything. No one chooses a framework (at least I don't) based on performance. You choose one framework over the other because you like the API and/or language. I myself am a framework author (giotto, a python framework that was not included in these benchmarks). If my framework had been included, I'm sure it would e…

Not sure why this is downvoted so badly, the comment is largely correct.

This benchmark is even less useful than alioth's shootout, I'm not sure why there is so much effort put into it :)

Re: Web Framework Benchmarks Round 4

#70
post #14

Wow, I should really give Go a try.

Agreed, but the language is sufficiently (edit) MORE verbose than Python that it is still a valid strategy to write in Python first, and then rewrite in Go for performance..

If go is less verbose, then why write it in a more verbose language first? The reality is, go and python are pretty much even for verbosity, and there is absolutely no benefit to writing your app in python first and then go. You'd be better off writing it in go and then rewriting it in go if you want the benefits of learning from your first attempt.
Post reply on HN