[zipy124]

Copying my comment from lobste.rs here:

I don't think the performance issues here are a result of Django. The author says only 2-3 requests per second (rps). Even in debug mode just using django runserver I can get 60~ rps on my $WORK repo. Part of this is likely their choice of only using '-c 1', which doesn't accurately represent a web workload.

For example on a local dev server I get (in format -c n. rps)

1. 58

2. 61

3. 55

as expected because we only have 1 worker, in debug with little caching.

but when looking at an example production config we see

1. 1: 11

2. 2: 23

3. 5: 54

4. 10: 95

5. 20: 153

6. 30: 165

7. 40: 177

8. 50: 192

and so on....

All of these are far in excess of the 2-3 observed by the author.

Note these will heavily depend on how many database hits you have per request as that is the majority of workload, as well as your http server such as using http 1/2/3, and the TLS settings used etc...