#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
-------------------------------------+-------------------------------------
Comment (by Marc Parizeau):
Replying to [comment:7 Simon Charette]:
Thanks for the suggestion. I've tried it and it does not seem to reduce
the execution time for my test case that has about 26K threads for it's
user. So, the limitation that you mention probably applies. I am still
trying to understand what might be going on (my mastery of SQL is somewhat
limited), and why Django 3.1 was doing better than 3.2 for my specific
query. Anyway, for the time being, I've decided to move on to other
problems, since this one is mostly severe for myself, and not for my
regular users who have access to only a subset of the available contents.
I worry, however, that the problem will only grow as more content is
added...
I've also tried indexing, but so far to no improvement.
If I eventually find a solution, I will report it here.
Thanks for your help!
--
Ticket URL: <https://code.djangoproject.com/ticket/33973#comment:8>
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/010701830a96aec7-28210e2c-a9f6-41e3-8c9f-f19438f93b42-000000%40eu-central-1.amazonses.com.
