3 ms·
I am not saying the author's remarks are not interesting, but they live in a vacuum. For most projects, the resources spent on the "serving" part of your web se
by laurent_du 2y ago
I am not saying the author's remarks are not interesting, but they live in a vacuum. For most projects, the resources spent on the "serving" part of your web service are a small portion of the actual expenses. In many cases, it's going to be less than 1%. Going from 0.1% to 0.01% is not a significant improvement.
A typical Django-based application has a lot of non Python code that is running separately and the performance of Django or Python itself are mostly irrelevant.
If your application is a TODO app and you have billions of users, maybe yeah.
- ashishb 2y ago> A typical Django-based application has a lot of non Python code that is running separately and the performance of Django or Python itself are mostly irrelevant. I have seen applications where this serving cost alone becomes dominant. And that's why I shared the YouTube story as well where the ~60X savings came from migrating from Python -> C++.
- laurent_du 2y agoI agree with you that for such an application, Python is probably not the right fit.