Re: [Django] #22608: Migrations optimizer slow (due to double working?)

[Django]

#22608: Migrations optimizer slow (due to double working?)
-+-
 Reporter:  David S  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  duplicate
 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 Mariusz Felisiak ):

 In [changeset:"25bf15c0dac3371be66db0173d26715b9f167529" 25bf15c]:
 {{{
 #!CommitTicketReference repository=""
 revision="25bf15c0dac3371be66db0173d26715b9f167529"
 Refs #22608 -- Made app_label required when optimizing migrations.

 This paved the way for the removal of lot of logic when app_label was
 not specified.
 }}}

-- 
Ticket URL: 
Django 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.14d07b2ba02b289b2c18429887a4d66b%40djangoproject.com.

Re: [Django] #22608: Migrations optimizer slow (due to double working?)

[Django]

#22608: Migrations optimizer slow (due to double working?)
-+-
 Reporter:  David S  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

 * status:  new => closed
 * resolution:   => duplicate


-- 
Ticket URL: 
Django 
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.d62ce16f8d04fa945f9794fd677a58b8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22608: Migrations optimizer slow (due to double working?)

[Django]

#22608: Migrations optimizer slow (due to double working?)
--+
 Reporter:  David S   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 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 Simon Charette):

 Things have improved significantly since this ticket was opened 4 years
 ago.

 `makemigrations` past improvements include

 1. Multiple tickets to avoid or delay model rendering during operation's
 `state_forwards`.
 2. #24554: Sped up migrations by rendering initial apps when they are
 first needed
 3. #29243: Improve efficiency of migration graph algorithm

 the last remaining path that causes slowdown during the `makemigrations`
 phase is the model rendering caused by the auto-detector. I just filed a
 ticket to cover that in #29899.

 The main slowdown during the `migrate` phase is the heavy model rendering
 required to pass ''fake'' models to the schema editor. Markus Holtermann
 have a long standing
 [https://github.com/django/django/compare/master...MarkusH:schemaeditor-
 modelstate branch to completely stop rendering models to during the
 migration phase]. That includes significant changes to the schema editor
 to be able to operate on model states instead of rendered model classes
 but it's a good step forward IMO. I just filed a ticket to track this
 optimization in #29898.

 Not sure if there is anything actionable in this ticket at this point. I'd
 suggest we close it and open more focused ones instead.

-- 
Ticket URL: 
Django 
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.3a3afcb165dfd73350d1a296e5d32afc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22608: Migrations optimizer slow (due to double working?)

[Django]

#22608: Migrations optimizer slow (due to double working?)
--+
 Reporter:  David S   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 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 Ramiro Morales):

 This might be of interest to the OP and people which contributed to this
 discussion particularly those which have posted reports of of their big
 Django projects with many migrations:

 There is more work on this migrations efficiency front:

 * Ticket: #29243
 * Pull request at GitHub: https://github.com/django/django/pull/9804
 * Post to the django-dev mailing list asking for test of the proposed
 changes (includes a profiling script): https://groups.google.com/d/msg
 /django-developers/PT86wX-oHKo/ZNRxt_E8BwAJ

-- 
Ticket URL: 
Django 
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.3a5aa6bff428968a5afd4211f9228f17%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22608: Migrations optimizer slow (due to double working?)

[Django]

#22608: Migrations optimizer slow (due to double working?)
--+
 Reporter:  davids|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 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 ipmb):

 Here's a cProfile of `manage.py makemigrations --empty myapp` on my i5
 macbook with SSD.

 * Django 1.9.1
 * ~80 migrations
 * ~300 tables

 {{{
 66325365 function calls (65778093 primitive calls) in 157.981 seconds
 }}}
 https://gist.github.com/ipmb/75be883defe09fc3dc32

--
Ticket URL: 
Django 
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.3bd7da7456982535735286b8f7a05ad0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22608: Migrations optimizer slow (due to double working?)

[Django]

#22608: Migrations optimizer slow (due to double working?)
--+
 Reporter:  davids|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 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
--+
Changes (by mvantellingen):

 * cc: michaelvantellingen@… (added)


--
Ticket URL: 
Django 
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.615b7e1613eca83023ffcb6249ca778f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22608: Migrations optimizer slow (due to double working?)

[Django]

#22608: Migrations optimizer slow (due to double working?)
--+
 Reporter:  davids|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 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 davidszotten):

 my project, which spawned this ticket has certainly improved

 when i raised the ticket:

 `17353606 function calls (17308702 primitive calls) in 39.818 seconds`
 vs
 `3650282 function calls (3640151 primitive calls) in 9.895 seconds`

 same code today (didn't re-run `makemigrations`; they are mostly the same
 38, + 10 new ones added in django

 `4268279 function calls (4178349 primitive calls) in 9.825 seconds`
 vs
 `3907185 function calls (3829169 primitive calls) in 9.213 seconds` (same
 old slow laptop)


 details:

 {{{
 Wed Jan  7 22:37:59 2015separate.dat

  4268279 function calls (4178349 primitive calls) in 9.825 seconds

Ordered by: internal time
List reduced from 553 to 15 due to restriction <15>

ncalls  tottime  percall  cumtime  percall filename:lineno(function)
 281601.3990.0002.2680.000
 
/Users/david/dev/django_source/django/db/models/fields/__init__.py:336(deconstruct)
   4711.2920.0031.2920.003 {method 'execute' of
 'psycopg2._psycopg.cursor' objects}
  50090.8000.0001.2560.000
 
/Users/david/dev/django_source/django/db/models/fields/related.py:309(swappable_setting)
 286720.7380.0001.0360.000
 
/Users/david/dev/django_source/django/db/models/fields/__init__.py:137(__init__)
 855100/8494760.5690.0000.5760.000 {getattr}
 193250.3050.0000.4480.000
 /Users/david/dev/django_source/django/db/models/options.py:721(_expire_cache)
940.2920.0030.2920.003 {method 'commit' of
 'psycopg2._psycopg.connection' objects}
 315340.2590.0005.6800.000
 
/Users/david/dev/django_source/django/db/migrations/state.py:396(construct_fields)
4076190.1890.0000.2320.000
 /Users/david/dev/django_source/django/db/models/options.py:348(swapped)
 61368/1880.1770.0000.7850.004
 
/usr/local/Cellar/python/2.7.3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/copy.py:145(deepcopy)
6906820.1440.0000.1470.000 {method 'get' of 'dict'
 objects}
1500510.1330.0000.1330.000 {delattr}
 144008/1440060.1280.0000.2990.000 {isinstance}
1664610.1270.0000.1270.000 {method 'update' of 'dict'
 objects}
 502200.1070.0000.2240.000
 /Users/david/dev/django_source/django/apps/config.py:168(get_models)
 }}}


 {{{
 squashed.dat% stats 15
 Wed Jan  7 22:44:14 2015squashed.dat

  3907185 function calls (3829169 primitive calls) in 9.213 seconds

Ordered by: internal time
List reduced from 546 to 15 due to restriction <15>

ncalls  tottime  percall  cumtime  percall filename:lineno(function)
   3921.4570.0041.4580.004 {method 'execute' of
 'psycopg2._psycopg.cursor' objects}
 254401.2020.0001.9800.000
 
/Users/david/dev/django_source/django/db/models/fields/__init__.py:336(deconstruct)
  48320.7730.0001.2260.000
 
/Users/david/dev/django_source/django/db/models/fields/related.py:309(swappable_setting)
 260280.7580.0001.0280.000
 
/Users/david/dev/django_source/django/db/models/fields/__init__.py:137(__init__)
 773770/7682620.5140.0000.5200.000 {getattr}
 216120.3390.0000.4950.000
 /Users/david/dev/django_source/django/db/models/options.py:721(_expire_cache)
 284220.2390.0005.2810.000
 
/Users/david/dev/django_source/django/db/migrations/state.py:396(construct_fields)
3979420.1850.0000.2270.000
 /Users/david/dev/django_source/django/db/models/options.py:348(swapped)
 52884/1640.1570.0000.7040.004
 
/usr/local/Cellar/python/2.7.3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/copy.py:145(deepcopy)
1681810.1460.0000.1460.000 {delattr}
6193220.1350.0000.1380.000 {method 'get' of 'dict'
 objects}
 130099/1300970.1150.0000.2650.000 {isinstance}
1513820.1140.0000.1140.000 {method 'update' of 'dict'
 objects}
 50.1100.0000.2360.000
 

Re: [Django] #22608: Migrations optimizer slow (due to double working?)

[Django]

#22608: Migrations optimizer slow (due to double working?)
--+
 Reporter:  davids|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 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 claudep):

 It would be nice to get an up-to-date profiling report with a big project
 to know the progress done with recent commits.

--
Ticket URL: 
Django 
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.3230ca73200b12ba70fa026c0f62554e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22608: Migrations optimizer slow (due to double working?)

[Django]

#22608: Migrations optimizer slow (due to double working?)
--+
 Reporter:  davids|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 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
--+
Changes (by timgraham):

 * has_patch:  1 => 0


Comment:

 Committed the PR, but no doubt more work can be done on this so leaving
 the ticket open.

--
Ticket URL: 
Django 
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.e95e7763cd0e426ea888eb82d95b1f9c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22608: Migrations optimizer slow (due to double working?)

[Django]

#22608: Migrations optimizer slow (due to double working?)
--+
 Reporter:  davids|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"12bf42ae0db752bf4a4387d6be7276cd145f59d1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="12bf42ae0db752bf4a4387d6be7276cd145f59d1"
 Refs #22608 -- Optimized migration optimizer

 Moved list constants instantiation into optimizer's __init__.
 }}}

--
Ticket URL: 
Django 
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.7bf5a9785c2e07df9ce9a6df7378b671%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22608: Migrations optimizer slow (due to double working?)

[Django]

#22608: Migrations optimizer slow (due to double working?)
--+
 Reporter:  davids|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"391bb09bb09e8208b4711c21e850b9351dd62989"]:
 {{{
 #!CommitTicketReference repository=""
 revision="391bb09bb09e8208b4711c21e850b9351dd62989"
 Refs #22608 -- Optimized migration optimizer and migrate by caching calls
 to str.lower()
 }}}

--
Ticket URL: 
Django 
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.f8dff5b36f6f804f5f863031db7ebbf8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22608: Migrations optimizer slow (due to double working?)

[Django]

#22608: Migrations optimizer slow (due to double working?)
--+
 Reporter:  davids|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by MarkusH):

 * needs_better_patch:  1 => 0


Comment:

 PR: https://github.com/django/django/pull/3830

--
Ticket URL: 
Django 
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.75f7abd429bd963a24be13767b827adc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22608: Migrations optimizer slow (due to double working?)

[Django]

#22608: Migrations optimizer slow (due to double working?)
--+
 Reporter:  davids|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 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
--+
Changes (by timgraham):

 * version:  1.7-beta-2 => master


--
Ticket URL: 
Django 
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.c66976ebd0c90b809b9482850f08%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22608: Migrations optimizer slow (due to double working?)

[Django]

#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:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by collinanderson):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1


--
Ticket URL: 
Django 
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.1fbca2abfdc784012d3da6e8cd566999%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22608: Migrations optimizer slow (due to double working?)

[Django]

#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: 
Django 
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.1566f1c7af3de173fe706633f3306196%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22608: Migrations optimizer slow (due to double working?)

[Django]

#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 Tilka):

 Please take a look at this related PR:
 https://github.com/django/django/pull/3540

--
Ticket URL: 
Django 
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.9092e3d125989f33410ad381adc0764b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22608: Migrations optimizer slow (due to double working?)

[Django]

#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 claudep):

 Slowness about the `migrate` process itself is separately tracked in
 #23745.

--
Ticket URL: 
Django 
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.bfbd8e7cbf4f2667cc3b9cd599947035%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22608: Migrations optimizer slow (due to double working?) (was: migrations slow (due to double working?))

[Django]

#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
-+-

--
Ticket URL: 
Django 
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.14f392d7023b66106fe5ec157bd20eaa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.