#24743: Django 1.8.1 migrations are actually slower than 1.8?
--------------------------------------+------------------------------------
Reporter: pzrq | Owner: MarkusH
Type: Cleanup/optimization | Status: assigned
Component: Migrations | Version: 1.8
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 petersanchez):
Has anyone tested the PR yet? I haven't had a chance to yet. Upgrading a
larger project from 1.7.x to 1.8.2 has migrations running very slow. See
output here (note, this is on my MacBook Air, PG9, etc.):
{{{
(env)macbook ~/development/houselogic/src/houselogic $ time ./manage.py
migrate --fake-initial
Operations to perform:
Synchronize unmigrated apps: google, rendertext, allauth, twitter,
linkedin, django_extensions, typogrify, django_mobile, audioplayer,
tinymce, cumulus, humanize, haystack, thumbnail, mptt, staticfiles,
sitemaps, facebook, edialog, pipeline, sitecatalyst, messages,
syndication, social_media
Apply all migrations: redirects, openid, realtors, accounts,
user_content, editorial_content, badges, layout, buying_selling, sites,
comments, blog, contenttypes, work_queue, sweepstakes, main, core,
django_comments, sessions, faq, auth, binder, news, account, admin,
contest, modules, recommendations, twitter_logger, socialaccount
Synchronizing apps without migrations:
Creating tables...
Running deferred SQL...
Installing custom SQL...
Running migrations:
Rendering model states... DONE
Applying account.0001_initial... FAKED
Applying account.0002_email_max_length... OK
Applying accounts.0004_auto_20150615_1533... OK
Applying auth.0003_auto_20150615_1533... OK
Applying badges.0003_auto_20150615_1533... OK
Applying django_comments.0002_update_user_email_field_length... OK
Applying blog.0004_auto_20150615_1533... OK
Applying buying_selling.0004_auto_20150615_1533... OK
Applying contenttypes.0002_remove_content_type_name... OK
Applying django_comments.0003_auto_20141110_1644... OK
Applying editorial_content.0007_auto_20150528_2042... OK
Applying editorial_content.0008_video_source... OK
Applying editorial_content.0009_navigationcategoryfeaturedlink_video...
OK
Applying editorial_content.0010_auto_20150618_1845... OK
Applying editorial_content.0010_auto_20150615_1533... OK
Applying editorial_content.0011_merge... OK
Applying layout.0004_homepagecarouselitem_video... OK
Applying layout.0005_auto_20150611_2216... OK
Applying modules.0003_auto_20150615_1533... OK
Applying news.0002_auto_20150615_1533... OK
Applying openid.0001_initial... FAKED
Applying realtors.0003_auto_20150615_1533... OK
Applying socialaccount.0001_initial... FAKED
real 7m4.016s
user 6m48.144s
sys 0m3.732s
}}}
The "Rendering model states" piece takes the longest. Over 5 minutes.
--
Ticket URL: <https://code.djangoproject.com/ticket/24743#comment:10>
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/062.a498bcba44e1ce3d1ad11266f8d4f853%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
