#33584: Encourage using persistent database connections
-------------------------------------+-------------------------------------
Reporter: Tom Carrick | Owner: Tom
| Carrick
Type: New feature | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* cc: Florian Apolloner (added)
* status: assigned => closed
* resolution: => needsinfo
Comment:
Hi Tom. Thanks for the suggestion here.
It looks like this has come up before, and there's a problem with
runserver compatibility: [https://groups.google.com/g/django-
developers/c/rH0QQP7tI6w/m/yBusiFTNBR4J mailing list post from 2013].
([https://groups.google.com/g/django-developers/search?q=CONN_MAX_AGE
Mailing list search for CONN_MAX_AGE])
Do these points still apply? If so, is there a way around them? Did anyone
explore the idea from the mailing list thread?
Also relevant is #33497 -- ''"Database persistent connections do not work
with ASGI in 4.0"'' — Question then: is it clear cut that persistent
connections are better — not just for this ASGI case but in general? (If
you have lots of traffic, sure, but... 🤷) From that ticket, I know
Florian is thinking about a connection pool, which would be connected.
Whilst generally it seems ''Sure, yeah'', I think some wider discussion is
needed, even if that just results in ''Clearly, yeah''.
(DevelopersMailingList :)
I'll mark this needs info in the meantime.
--
Ticket URL: <https://code.djangoproject.com/ticket/33584#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107017fbb978c8f-88a6277e-1117-414c-8f65-bc386b907507-000000%40eu-central-1.amazonses.com.
