7 ms·
These are fun benchmarks, but every single framework in the top 250 or so is more than fast enough for most apps. Even the slowest in the list manages 366/reque
by onion2k 8y ago
These are fun benchmarks, but every single framework in the top 250 or so is more than fast enough for most apps. Even the slowest in the list manages 366/requests per second, which is probably enough to prove an idea before optimizing for speed.
We're approaching the point where speed is essentially a solved problem unless you're at Google-scale.
- lllr_finger 8y agoIs it? Concurrent connection handling at scale is a major problem, and plenty of Fortune 1000 companies would jump at the chance to have even 5% fewer instances deployed. 366 rps in a test scenario doesn't scratch the surface of what I need, and I'm not doing anything I'd consider crazy scale. When you need to support hundreds of thousands of rps, small improvements can be very noticeable.
- bpicolo 8y ago> plenty of Fortune 1000 companies would jump at the chance to have even 5% fewer instances deployed. Becoming a Fortune 1000 company isn't "most apps"
- mkirklions 8y agoI'll tell you what. When I'm a fortune 10,000 company, we can afford to rewrite the web app.
- ddorian43 8y agoBut do they rewrite ? Twitter did. Facebook didn't.
- chipotle_coyote 8y agoFacebook wrote a new PHP VM and forked the language, so while it may not technically be rewriting...
- tomnipotent 8y ago> Facebook didn't. You have no idea what you're talking about. Not only did they produce TWO different implementations of PHP (HHVM and Hack), a vast majority of their infrastructure is NOT in PHP (which is mostly reserved for the front-end/web tier).
- ddorian43 8y agoI know. Still, cheaper than rewrite.
- smoe 8y agoI agree with the overall sentiment. Plus almost all cases I run into performance issues with e.g. Python in general web development, that main problems were how the code was written, not what it was written in and being bottle-necked by the database. That said I disagree a bit with saying it is a a solved problem unless you are Google-scale. In developing countries if you are in a small company without big investors, you need to do quite a bit more juggling with infrastructure budgets once you are past MVP compared to for example where I'm from Switzerland.
- mkirklions 8y agoIm somewhat traditional with my web, javascript and php. But are people really doing python and web development? I love python for my web crawlers, photoshop automation, and table formatting automation- But I never considered it a web contender. Any major sites running python? Whats the popular way people are doing it?
- onion2k 8y agoAny major sites running python? YouTube is quite a popular one.
- conradfr 8y agoIsn't Django huge? And there's Flask as well.
- detaro 8y agoInstagram uses Python/Django a lot
- tomchristie 8y agoHell yes - it's an incredibly productive language, and the Web frameworks for it (Flask & Django in particular) are really nicely mature. For fast Web App development it's a superb language choice. Not so good if you wanted to write a super-high-throughput proxy service, but asyncio & ASGI is starting to change things there too. > Any major sites running python? Instagram is probably the biggest headliner these days, but there's stacks of others.
- ekr 8y agoUntil your app gets on HN/Slashdot/Reddit etc and experiences the hug of death. Jokes aside, I do agree that from a developer's standpoint, the optimal way to act (optimising for business success) is as you say, ignore performance at first. But from an engineering/craftsmanship standpoint, it should really bother you to have an inefficient system. Just think of all that extra CPU load, and all the CO2, all the coal burnt to sustain it ...
- l1ambda 8y agoIt's not so much about immediate performance, but about headroom. The blog post https://www.techempower.com/blog/ https://www.techempower.com/blog/ puts it better than I: > I argue that if you raise the framework's performance ceiling, application developers get the headroom—which is a type of luxury—to develop their application more freely (rapidly, brute-force, carefully, carelessly, or somewhere in between). In large part, they can defer the mental burden of worrying about performance, and in some cases can defer that concern forever. Developers on slower platforms often have so thoroughly internalized the limitations of their platform that they don't even recognize the resulting pathologies: Slow platforms yield premature architectural complexity as the weapons of “high-scale” such as message queues, caches, job queues, worker clusters, and beyond are introduced at load levels that simply should not warrant the complexity.
- pier25 8y agoI agree with your general point, but there are many more companies and products that do require high performance beyond Google.