Hi Dan.
Super!
On Tuesday, 28 August 2018 17:28:32 UTC+2, d...@thread.com wrote:
>
> I've run it on our codebase with ~1100 migrations and ~380 apps.
>
Yes! This is what I was looking for.
> There were no exceptions thrown - the script completed cleanly, although I
> haven't actually
Hi Carlton,
Adam asked me to take a look at this. I've run it on our codebase with
~1100 migrations and ~380 apps.
Running on Django 2.1, the results of this script (the updated version) are:
> 1min 23s ± 1.1 s per loop (mean ± std. dev. of 7 runs, 1 loop each)
Running on the branch,
Making the script less noisy here I commented out the actual work.
(So it didn't function as a test.)
(No comment. )
Corrected version:
```
import sys
from django.db import connection
from django.db.migrations.loader import MigrationLoader
loader = MigrationLoader(connection)
backwards =
Thanks Jeff. Super.
(PR is fine )
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Hi Carlton,
I think I have a reasonable candidate for this and will try to find some
time to do the comparison this week. I'll post results on the PR, or here
if you prefer, upon completion.
Jeff
On Thursday, July 26, 2018 at 7:45:45 AM UTC-6, Carlton Gibson wrote:
>
> Hi all.
>
> Do you
Hi all.
Do you have a project with a slow and complicated migration history?
If so, any chance you could lend a brief hand testing?
See https://github.com/django/django/pull/9804
This refactors the migration graph algorithm and in principle should make
it significantly faster.
(More or less
