#36869: Optimise migration graph planning
-------------------------------------+-------------------------------------
     Reporter:  James Fysh           |                    Owner:  (none)
         Type:                       |                   Status:  new
  Cleanup/optimization               |
    Component:  Database layer       |                  Version:  dev
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:  migration digraph    |             Triage Stage:  Accepted
  loader                             |
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):

 * cc: Nick Pope (added)

Comment:

 I started the triage for this ticket and I truly wanted to see the
 numbers. I built a benchmarking script, and got this numbers:

 * code from `main`:
 {{{
 compare   100 against   200 migrations (2.0x size): 2.92x time
 compare   200 against   400 migrations (2.0x size): 3.40x time
 compare   400 against   800 migrations (2.0x size): 3.75x time
 compare   800 against  1600 migrations (2.0x size): 3.69x time
 compare  1600 against  3200 migrations (2.0x size): 3.96x time
 }}}

 * code from the proposed PR:
 {{{
 compare   100 against   200 migrations (2.0x size): 1.87x time
 compare   200 against   400 migrations (2.0x size): 2.01x time
 compare   400 against   800 migrations (2.0x size): 2.06x time
 compare   800 against  1600 migrations (2.0x size): 2.10x time
 compare  1600 against  3200 migrations (2.0x size): 1.97x time
 }}}

 * code proposed from Nick:
 {{{
 compare   100 against   200 migrations (2.0x size): 1.75x time
 compare   200 against   400 migrations (2.0x size): 2.22x time
 compare   400 against   800 migrations (2.0x size): 2.12x time
 compare   800 against  1600 migrations (2.0x size): 1.77x time
 compare  1600 against  3200 migrations (2.0x size): 2.13x time
 }}}

 Perhaps we should consider Nick's suggestion to keep the logic a little
 more straightforward?
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36869#comment:3>
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 visit 
https://groups.google.com/d/msgid/django-updates/0107019bc7b469b4-c00da9e4-3c9f-45db-bcd5-c0f0cf036c07-000000%40eu-central-1.amazonses.com.

Reply via email to