Re:Bjoern: A screamingly fast Python WSGI server written in C.
by detst on Friday December 24, 2010 @11:46AM
(#2037491)
> 200 hours trying to reduce that 3% to 2.5%
It's about progression over time. If someone didn't do it, we'd be leaving significant performance gains behind. That means more servers, more electricity and more money for everyone.
I'm not going to do that for my app but it's nice that there are people making these improvements for the benefit of everyone that uses their server.
When you take into account many small improvements, across all deployments, over time, they can and do add up to significant improvements.
Re:Bjoern: A screamingly fast Python WSGI server written in C.
by d0mine on Friday December 24, 2010 @10:58AM
(#2037414)
Amdahl's law http://en.wikipedia.org/wiki/Amdahl%27s_law
Re:Bjoern: A screamingly fast Python WSGI server written in C.
by yashh on Friday December 24, 2010 @11:21AM
(#2037440)
Totally agree with you. You dont really get 1000's of reqs/sec in a real world environment. All you need is a good server which is fast and memory efficient. Rest of the efforts should be focussed on the webapp side, more importantly DB. If you can work on your IO you will have a fast and efficient application.
Even assuming unlimited developer resources, will you really notice a 0.5% difference in production, especially when taking things like network latency into account?
My point is that hyping over raw performance is misleading at best. If performance is the only thing that matters then we wouldn't have operating systems with abstractions - everybody would program against the bare metal in assembly. One should weight the pros and cons carefully and reach a balanced trade-off.