#33497: Database persistent connections do not work with ASGI in 4.0
-------------------------------------+-------------------------------------
Reporter: Stenkar | Owner: (none)
Type: New feature | Status: new
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: ASGI, Database, | Triage Stage: Accepted
async |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by dseb):
Replying to [comment:43 Florian Apolloner]:
> This make sense, a small timeout value increases the chance to see this
error if you are already running out of connections.
My mistake, I meant to say "large timeout value". My containers each
answer ~2 requests per second, average response time is about 400ms. It
shouldn't take many connections to service this workload (even one
connection should work, I think), and yet, with pool timeouts set to 30s
and the pool max size set to 16, I'm seeing many such errors. Which is why
it seems to me that the new pooling support hasn't solved this particular
problem.
--
Ticket URL: <https://code.djangoproject.com/ticket/33497#comment:44>
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/0107019248545c86-f07f326e-9ba6-4e42-90c2-e228ec1caf80-000000%40eu-central-1.amazonses.com.
