Opened 12 years ago
Last modified 12 years ago
#20481 new New feature
Provide official hooks for execution profiling
Reported by: | Michael van Tellingen | Owned by: | nobody |
---|---|---|---|
Component: | Core (Other) | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | rob@… | Triage Stage: | Accepted |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Pull Requests: | How to create a pull request | ||
Description ¶
There are various django apps which monkeypatch Django internals to add profiling for statistics. These are of course well known apps like django-debug-toolbar, django-mozilla-statsd etc.
I think a much cleaner solution is to provide official hooks instead of monkey-patches on top of monkey-patches :-)
Currently thinking about:
- Database Cursor, for tracking execution time of sql
- Template rendering time
- Cache retrieval etc.
I'm willing to create a patch if there is any interest.
According to the ticket's flags, the next step(s) to move this issue forward are:
- To provide a patch by sending a pull request. Claim the ticket when you start working so that someone else doesn't duplicate effort. Before sending a pull request, review your work against the patch review checklist. Check the "Has patch" flag on the ticket after sending a pull request and include a link to the pull request in the ticket comment when making that update. The usual format is:
[https://github.com/django/django/pull/#### PR]
.
Change History (2)
comment:1 by , 12 years ago
Component: | Uncategorized → Core (Other) |
---|---|
Triage Stage: | Unreviewed → Accepted |
comment:2 by , 12 years ago
Cc: | added |
---|
Note:
See TracTickets
for help on using tickets.
I'm going to mark this accepted based on the principle that extension APIs for real-world use cases are always welcome, and profiling definitely qualifies as a real-world use case.
However, this needs specifics.