Repository navigation
Release 1.9.1 - #139
Merged
Merged
Release 1.9.1#139
Conversation
PhiLily
force-pushed
the
release/1.9.1
branch
from
October 16, 2026 21:00
42cdfab to
cb791fb
Compare
**What and why:** Warn at worker start on PostgreSQL when `CONN_MAX_AGE` is 0 and no `OPTIONS["pool"]` is set, because every task then opens a new database connection. Rewrite "Retaining worker connections" in the production guide to give both settings and the pool size to use. Retry an outcome write whose connection is refused, with waits of 50 ms doubling to 1.6 s. The waits total at most a tenth of `LOCK_TIMEOUT`. A worker told to stop ends a wait at once. Replace the benchmarks page with a run of django-ox 1.9.0 against django-tasks-db 0.13.0 at the same connection settings: 1.4 to 1.7 times the tasks per second with pooled or persistent connections. The rows are in `benchmarks/results-raw-2026-10-14-matched.json`, and `benchmarks/render_results.py` checks every number on the page against them. Rewrite sentences on the README and the front-door docs pages to state the point directly. **Operator action:** none. A worker on PostgreSQL with `CONN_MAX_AGE = 0` and no pool logs one warning at start. Set `CONN_MAX_AGE = 600`, or set `OPTIONS["pool"]` and leave `CONN_MAX_AGE` at 0. No database migration is required.
PhiLily
force-pushed
the
release/1.9.1
branch
from
October 16, 2026 21:33
cb791fb to
96947c6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why:
Warn at worker start on PostgreSQL when
CONN_MAX_AGEis 0 and noOPTIONS["pool"]is set, because every task then opens a new database connection. Rewrite "Retaining worker connections" in the production guide to give both settings and the pool size to use.Retry an outcome write whose connection is refused, with waits of 50 ms doubling to 1.6 s. The waits total at most a tenth of
LOCK_TIMEOUT. A worker told to stop ends a wait at once.Replace the benchmarks page with a run of django-ox 1.9.0 against django-tasks-db 0.13.0 at the same connection settings: 1.4 to 1.7 times the tasks per second with pooled or persistent connections. The rows are in
benchmarks/results-raw-2026-10-14-matched.json, andbenchmarks/render_results.pychecks every number on the page against them.Rewrite sentences on the README and the front-door docs pages to state the point directly.
Operator action: none. A worker on PostgreSQL with
CONN_MAX_AGE = 0and no pool logs one warning at start. SetCONN_MAX_AGE = 600, or setOPTIONS["pool"]and leaveCONN_MAX_AGEat 0.No database migration is required.