Changes between Version 5 and Version 6 of Ticket #31373
- Timestamp:
- Mar 17, 2020, 4:13:00 PM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #31373 – Description
v5 v6 15 15 - CONN_MAX_AGE = 30, starting `runserver` and making many calls with `ab -c 10 -n 100 http://127.0.0.1:8000/` uses all available connections and ends with error 500 (due to no available connections) 16 16 - CONN_MAX_AGE = 30, starting `runserver --nothreading` and making calls with `ab -c 100 -n 100 http://127.0.0.1:8000/` works fine 17 17 - CONN_MAX_AGE=30 + runserver + ab scenario is reproducible on clean install. Called view must access database. 18 - CONN_MAX_AGE=0 + runserver + ab -> cannot reproduce. 19 - Django 2.x has similar issue for CONN_MAX_AGE=30, but can reuse connections (still there are several errors on high traffic, but app server can "recover" and handle bunch of incoming requests) 20 - Looks like Django 3.x cannot reuse connections 18 21 19 CONN_MAX_AGE=30 + runserver + ab scenario is reproducible on clean install. View must call database. 20 CONN_MAX_AGE=0 + runserver + ab -> cannot reproduce. 22 `ab -c 10 -n 200 ` Django 3.0.4: 23 Complete requests: 200 24 Failed requests: 108 25 26 `ab -c 10 -n 1000` Django 2.2.11: 27 Complete requests: 1000 28 Failed requests: 37