#33973: Performance regression when moving from 3.1 to 3.2
-------------------------------------+-------------------------------------
Reporter: Marc Parizeau | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: performance | Triage Stage:
regression | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* cc: Simon Charette (added)
* resolution: => needsinfo
* status: new => closed
* component: Uncategorized => Database layer (models, ORM)
Comment:
Using `EXISTS` to exclude multi-valued relationship was introduced in
8593e162c9cb63a6c0b06daf045bc1c21eb4d7c1. However this should be is easier
to optimize for query planers, it's not clear to me why you're facing a
performance regression. Perhaps the query plan should be regenerated or
this is an issue in PostgreSQL 14.2. I don't think there is anything that
we could improve in Django.
--
Ticket URL: <https://code.djangoproject.com/ticket/33973#comment:5>
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/01070182fa66433f-3681fa6d-deb6-4856-8824-c79c50dd2e14-000000%40eu-central-1.amazonses.com.
