#22608: Migrations optimizer slow (due to double working?)
-------------------------------------+-------------------------------------
Reporter: davids | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version:
Component: Migrations | 1.7-beta-2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by UloPe):
This PR https://github.com/django/django/pull/3545 speeds up the optimizer
by about 60% simply by pulling out the creation of two utility lists from
function to module scope and caching the result of calling .lower() on the
.name, .old_name, .new_name and .module_name attributes in Operation
subclasses.
--
Ticket URL: <https://code.djangoproject.com/ticket/22608#comment:13>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.1566f1c7af3de173fe706633f3306196%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.