News for hackers. Stuff that matters.

A comment on Django 3. Parent comment

Re:Django 3 by qxnqd on Monday December 02, 2019 @10:05AM (#21682928)
Of course, if you are incompetent enough to write queries that use no indexes and you don't detect that before you push to prod, you will have problems there.

What I mean is: when you start optimising, no matter how well you do, you will eventually hit a CPU performance wall. Then you will realise that only a rewrite will get you out of that hole, and by then it will be late.

[ Parent | on HN ]
Re:Django 3 by acdha on Monday December 02, 2019 @10:23AM (#21683130)
In my experience, many sites never hit that point of having CPU-bound Python code which they can’t afford; the ones which do hit that wall are usually large enough that they can carve out room for a C/Rust library, microservice, etc. rather than rewriting the entire thing.
[ Parent | on HN ]
Re:Django 3 by frankwiles on Monday December 02, 2019 @09:11PM (#21689313)
I concur, I’ve worked on at least a dozen “web scale” Django sites and I can’t think of a single one where we were CPU bound.
[ Parent | on HN ]