#26284: Improve django.setup() and app loading performance
--------------------------------------+--------------------
Reporter: Miserlou | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (Other) | Version: 1.9
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+--------------------
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.
This ticket is for discussing 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?
--
Ticket URL: <https://code.djangoproject.com/ticket/26284>
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/051.94f4e9e54a0139a107da7fd3bd6ae4e7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
