HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
robhudson
django-debug-toolbar
Python2009–2011
robhudson / django-debug-toolbar

django-debug-toolbar

Now maintained at the following URL:

Web Development
Explore on GitHubRead Hacker News discussions
4Distinct people
4Mentions
0Explicit recommenders
410GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Now maintained at the following URL:

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:56:55 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month4 dated mentions

Observed mentions: 2009-03-12 13:45:52 UTC to 2011-02-15 09:18:11 UTC.

012009-03-01 00:00:00 UTC to 2009-04-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 20092009-04-01 00:00:00 UTC to 2009-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-05-01 00:00:00 UTC to 2009-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-06-01 00:00:00 UTC to 2009-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-07-01 00:00:00 UTC to 2009-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-08-01 00:00:00 UTC to 2009-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-09-01 00:00:00 UTC to 2009-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-10-01 00:00:00 UTC to 2009-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-11-01 00:00:00 UTC to 2009-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-01 00:00:00 UTC to 2010-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-01-01 00:00:00 UTC to 2010-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-02-01 00:00:00 UTC to 2010-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 20102010-03-01 00:00:00 UTC to 2010-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-04-01 00:00:00 UTC to 2010-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-05-01 00:00:00 UTC to 2010-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-06-01 00:00:00 UTC to 2010-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-07-01 00:00:00 UTC to 2010-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-01 00:00:00 UTC to 2010-09-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2010-09-01 00:00:00 UTC to 2010-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-10-01 00:00:00 UTC to 2010-11-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2010-11-01 00:00:00 UTC to 2010-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-12-01 00:00:00 UTC to 2011-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-01-01 00:00:00 UTC to 2011-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-02-01 00:00:00 UTC to 2011-03-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 2011

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 20092009-03-01 00:00:00 UTC2009-04-01 00:00:00 UTC101
Apr 20092009-04-01 00:00:00 UTC2009-05-01 00:00:00 UTC000
May 20092009-05-01 00:00:00 UTC2009-06-01 00:00:00 UTC000
Jun 20092009-06-01 00:00:00 UTC2009-07-01 00:00:00 UTC000
Jul 20092009-07-01 00:00:00 UTC2009-08-01 00:00:00 UTC000
Aug 20092009-08-01 00:00:00 UTC2009-09-01 00:00:00 UTC000
Sep 20092009-09-01 00:00:00 UTC2009-10-01 00:00:00 UTC000
Oct 20092009-10-01 00:00:00 UTC2009-11-01 00:00:00 UTC000
Nov 20092009-11-01 00:00:00 UTC2009-12-01 00:00:00 UTC000
Dec 20092009-12-01 00:00:00 UTC2010-01-01 00:00:00 UTC000
Jan 20102010-01-01 00:00:00 UTC2010-02-01 00:00:00 UTC000
Feb 20102010-02-01 00:00:00 UTC2010-03-01 00:00:00 UTC000
Mar 20102010-03-01 00:00:00 UTC2010-04-01 00:00:00 UTC000
Apr 20102010-04-01 00:00:00 UTC2010-05-01 00:00:00 UTC000
May 20102010-05-01 00:00:00 UTC2010-06-01 00:00:00 UTC000
Jun 20102010-06-01 00:00:00 UTC2010-07-01 00:00:00 UTC000
Jul 20102010-07-01 00:00:00 UTC2010-08-01 00:00:00 UTC000
Aug 20102010-08-01 00:00:00 UTC2010-09-01 00:00:00 UTC101
Sep 20102010-09-01 00:00:00 UTC2010-10-01 00:00:00 UTC000
Oct 20102010-10-01 00:00:00 UTC2010-11-01 00:00:00 UTC101
Nov 20102010-11-01 00:00:00 UTC2010-12-01 00:00:00 UTC000
Dec 20102010-12-01 00:00:00 UTC2011-01-01 00:00:00 UTC000
Jan 20112011-01-01 00:00:00 UTC2011-02-01 00:00:00 UTC000
Feb 20112011-02-01 00:00:00 UTC2011-03-01 00:00:00 UTC101

What Hacker News says

1 sources
zeemonkee·Feb 15, 2011
With Django - or any ORM it's a good idea to keep an eye on the SQL that your application is running. Use the django debug toolbar[1] and run your SQL queries against a profiler. Most of the time, that's where your serious bottlenecks will be. If a query happens to be a bottleneck, there are ways the ORM can improve performance (e.g. select_related() to reduce the number of queries in a loop, only() and defer() to reduce the number of columns in a query, and so on[2]. In some cases this may even involve using pure SQL or caching heavily used queries. Look at using processes vs threads with mod_wsgi, which should help improve performance. Ultimately however you might find nginx a better option, particularly if you are using it for static media/load balancing anyway. I'd suggest uwsgi (also heard good things about gunicorn). Use supervisord
Read the rest
or another process monitor to make sure the lights stay on. [1] https://github.com/robhudson/django-debug-toolbar [2] http://docs.djangoproject.com/en/dev/ref/models/querysets
In 12,000 Requests per second with Nginx, PHP and Memcached

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.