#23372: Test suite initial database construction is too slow
--------------------------------------+------------------------------------
Reporter: manfre | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Testing framework | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by akaariai):
A yet new alternate approach is here:
https://github.com/django/django/pull/5905. The idea is to skip disabling
constraints when no fixture files are found in loaddata. The 1.8 test
suite runs in 2500 seconds on my laptop after the patch (plus one line fix
in django-mssql, see the pull request).
The previously proposed alternate approach takes off another 10 minutes
from the runtime of the test suite on mssql, yielding a runtime of around
30 minutes. The changes needed there are a lot more invasive, as we will
need to pre-walk the objects in the fixture files. This could lead to
performance problems. The change might be worth it for master branch, but
backpatching seems too risky.
--
Ticket URL: <https://code.djangoproject.com/ticket/23372#comment:16>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.b178f4f6366d272893e8b5bc9c4e9027%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
