Ugh. As a strong advocate of both django and zappa, I'd love it if we could keep the conversation on target without degenerating into stack attacks. If you don't want to weigh in, please feel no obligation to do so.
I do agree that we could pare down the profile into more actionable sections. I'll see if I can get something a bit more preprocessed in the near future. Perhaps that will help keep this thread on target. On Friday, February 26, 2016 at 1:34:46 PM UTC-8, Florian Apolloner wrote: > > > > On Friday, February 26, 2016 at 9:53:00 PM UTC+1, Rich Jones wrote: >> >> @Aymeric >> > In my opinion, the first concrete step would be to measure how much >> time is spent executing Django code rather than importing Python modules. >> >> Over 70% of the total request time is spent in django.setup() - so you >> can see why we have an incentive to improve this! >> > > That profile looks somewhat worthless imo, please provide it in a usable > form, ie cProfile output. As Aymeric pointed out, most of the time in setup > is most likely spent in importing python modules, which is nothing we can > do about. > > >> You're halfway there, but the process is more complicated than that. The >> code is cached, not the internal state of the machine. You can follow our >> progress here: https://github.com/Miserlou/django-zappa/ >> > > What does this even mean? "code is cached"?! "internal state"!? which > internal state? > > >> But - another type caching could be another possibility. Can anybody >> think of any arrangements where we could perhaps call setup() with >> "pre-loaded"/cached applications? >> > > Use a sane application stack? :D > -- 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/0093ead4-21e7-417a-b9e4-e331307dd312%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
