-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Analyze Profiler Output #24
Comments
Well, right off the bat it looks like: (call)| 1| 2.70472| 2.70472| 71.79%|# /private/var/folders/00/vp4bg2md3ng4sqkg3hrz_j1003frjd/T/pip-build-iHBwmU/Django/django/init.py:8 setup 70% of the time is spent setting up Django. That seems like a good starting point. The majority of the rest is in (call)| 1| 1.04399| 1.04399| 27.71%|# /private/var/folders/00/vp4bg2md3ng4sqkg3hrz_j1003frjd/T/pip-build-iHBwmU/Django/django/core/handlers/wsgi.py:162 call and everything else looks pretty trivial. |
In setup(), populate eats the most.. |
Poking @stephrdev in case you have any insights/magic tricks you can think of to throw at this! |
Ticket for upstream discussion: https://code.djangoproject.com/ticket/26284 |
We got this down to ~30ms. |
@Miserlou can you provide more details on how you optimized this? |
Hi @sridhar562345 The new, official, and actively managed Zappa project is here. |
This ended up being way more detailed than I anticipated.
profile.txt
The text was updated successfully, but these errors were encountered: