I'm not sure we can load apps in parallel -- they are loaded in the order in which they appear in INSTALLED_APPS so the process is consistent. Maybe it would work for some setups, but I guess it would introduce subtle bugs in others.
https://docs.djangoproject.com/es/stable/ref/applications/#how-applications-are-loaded On Friday, February 26, 2016 at 10:36:57 AM UTC-5, Rich Jones wrote: > > (Originally posted this as a ticket, but we can have discussion here and > leave the ticket <https://code.djangoproject.com/ticket/26284> for just > more specific discussion.) > > I imagine that this is an area that hasn't really been given much > consideration with regards to optimization, because it isn't relevant to > normal Django deployments. However, with "serverless" deployments (those > without any permanent infrastructure), this becomes quite relevant as we > have to call setup() every request. > > > So, I'd love to discuss ideas for performance optimizations to Django's > setup method. (A sample output for profile is available here: > https://github.com/Miserlou/django-zappa/issues/24 ) > > > For starters - can we load apps in parallel? > -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/8fcafc86-4ae0-4fc8-a68b-02a2d911d3c9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
