[CentralOH] Profiling Django Apps?
nick.albright at gmail.com
Thu Aug 25 20:10:06 CEST 2011
<G> Heck, what'd I'd love is like a python profiler type output (Well, I
think I'd love that, but I may rue that day ;)
Initial look through, the resource usage (http://dpaste.com/602618/) generally
seems to be like .5 sec CPU time, and 2.5 sec elapsed time. (2.5 secs for
just raw/initial HTML is the obvious bottleneck)
Then 12 SQL queries taking like .4 to .9 ms each
And the html is < 1K lines.
And this is before any JS gets processed by the browser. Just the initial
I'm currently wildly guessing that it may be the boto library I'm using for
the amazon S3? But would love more solid info.
On Thu, Aug 25, 2011 at 1:48 PM, Issac Kelly <issac.kelly at gmail.com> wrote:
> What else do you want out of DDT? I've found that between the cache panel,
> and the SQL panel, I've been able to find most of my problems, my worst
> problems have been a result of not properly using select_related, or
> iterating over big querysets.
> If it's slow, but not showing up in DDT, it could be one of several things:
> * Really, Really big pages (>10k lines) the template engine seems to crap
> out on some of this
> * Bad/Really Big JS.
> On Thu, Aug 25, 2011 at 1:42 PM, Nick Albright <nick.albright at gmail.com>wrote:
>> Hello Everybody!
>> I was wondering if anyone had any experience with profiling django apps.
>> Things seem to be taking longer than I'd like in my one app, and I'm trying
>> to figure out where the bottleneck may be. And was wondering if anyone has
>> done this before? (I'm using django-debug-toolbar, which doesn't give me
>> enough info)
>> Just curious!
>> CentralOH mailing list
>> CentralOH at python.org
> CentralOH mailing list
> CentralOH at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the CentralOH