←back to thread

33 points ashishb | 3 comments | | HN request time: 0s | source
1. laurent_du ◴[] No.43298813[source]
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.
replies(1): >>43303090 #
2. ashishb ◴[] No.43303090[source]
> 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++.

replies(1): >>43313527 #
3. laurent_du ◴[] No.43313527[source]
I agree with you that for such an application, Python is probably not the right fit.