Opened 9 years ago
Closed 9 years ago
#26284 closed Cleanup/optimization (needsinfo)
Improve django.setup() and app loading performance
Reported by: | Rich Jones | Owned by: | nobody |
---|---|---|---|
Component: | Core (Other) | Version: | 1.9 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Someday/Maybe | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
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?
Change History (3)
comment:1 by , 9 years ago
Triage Stage: | Unreviewed → Someday/Maybe |
---|
comment:2 by , 9 years ago
For the record, here's the topic: https://groups.google.com/forum/#!topic/django-developers/TN4QJkcuMow
It doesn't seem like an issue anymore to me, since you should not be calling setup() every time (which was the end of the discussion, since there was a way to avoid calling it on every request).
comment:3 by , 9 years ago
Resolution: | → needsinfo |
---|---|
Status: | new → closed |
Generally, it's better to raise broad ideas on the DevelopersMailingList and open tickets for specific action items.