Opened 4 years ago

Closed 3 years ago

#20215 closed New feature (fixed)

Consider disabling persisent connections by default

Reported by: Aymeric Augustin Owned by: Aymeric Augustin
Component: Database layer (models, ORM) Version: master
Severity: Release blocker Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


Discussion here:

We must adress this one way or another before 1.6.

Change History (4)

comment:1 Changed 3 years ago by Aymeric Augustin

I'm now leaning towards disabling persistent connections by default, and suggesting them in the deployment checklist.

They're useless in development, because the development server spawns a new thread for each request. Worse, if the GC doesn't jump into action fast enough, it's easy to exhaust the number of available connections, and the result is a failure to load some static files. Annoying and non-obvious.

Also, I'm not comfortable with the idea of breaking the sites of people who won't read the release notes, won't understand the consequences for them, or (gasp!) use runserver in production (some might be doing that in spite of our warnings).

comment:2 Changed 3 years ago by Aymeric Augustin

<carljm> mYk: I think that's the right answer on #20215 (disabling by default).

comment:3 Changed 3 years ago by Aymeric Augustin

Status: newassigned

comment:4 Changed 3 years ago by Aymeric Augustin <aymeric.augustin@…>

Resolution: fixed
Status: assignedclosed

In 3d595c3bc38cf939503b69ce7a2802d5663f85b9:

Fixed #20215 -- Disabled persistent connections by default.

Note: See TracTickets for help on using tickets.
Back to Top