#14640: Add elapsed request time to the development server log
------------------------------------+---------------------------------------
Reporter: vaughnkoch | Owner: vaughnkoch
Status: assigned | Milestone: 1.3
Component: HTTP handling | Version: 1.2
Resolution: | Keywords: log time development
server
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Comment (by gabrielhurley):
Personally, I'm -0 on it...
1. There are numerous other (better) tools for telling you how long a
whole request took: firebug and the chrome developer console spring to
mind immediately. I'd much rather look at their graphical output of that
data.
2. The overall time taken by an individual request isn't going to tell
you anything useful except in the case of a *very* long (possibly broken)
request-response cycle.
3. Following on 2, there are much better tools for profiling python code,
in much more granular ways... at the very least, for profiling purposes,
you need to know how much time was spent in which pieces of code, not the
overall request time.
4. The time it takes to serve an individual request varies somewhat, and
may be affected by other disk/CPU activity. Proper profiling requires
averages across numerous repetitions of the same code.
5. Adding this function is just an extra bit of overhead (albeit minor)
for each request served by the dev server.
While I'm +1 on making profiling easier, I don't see this as being a
significant improvement. At the same time, I don't see any substantial
downsides (other than those noted by PaulM) to adding it. Hence my -0.
--
Ticket URL: <http://code.djangoproject.com/ticket/14640#comment:4>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
