OK, so I'm running a small internal web site that serves up reporting
information on some tests we're running. The main table of our
database has about 50,000 rows right now not a gigantic number, but
non-trivial. Thing is, even with simple views (i.e. the built-in
djago.views.generic.date_based.archive_* views) and bare-bones
templates (just a basic HTML layout), we are getting staggeringly bad
performance, even when displaying the year or month archives. I fire
up 'top' to watch what the processes are doing, and while I do notice
MySQL doing some hard chugging, most of the churning appears to be
going on in Python itself, which makes me believe that we are doing
something very inefficiently. Here's a clip of our urls.py:
from django.conf.urls.defaults import *
from myproject.tests.models import TestResult, TestSuite
import datetime
info_dict = {
'queryset': TestResult.objects.all(), # about 50,000 entries
'date_field': 'run_date',
}
today = datetime.date.today()
urlpatterns = patterns('',
# Static stuff
(r'^reports/site_media/(?P<path>.*)$', 'django.views.static.serve',
{'document_root': '/home/paarestad/heisenbug/media'}),
# Calendar view for month summary
(r'^reports/archive/(?P<y>\d{4})/(?P<m>\d{1,2})/$',
myproject.tests.views.change_calendar'),
#Date Based Generic View Links
(r'^reports/archive/$',
'django.views.generic.date_based.archive_index',
dict(info_dict)),
(r'^reports/archive/(?P<year>\d{4})/$',
'django.views.generic.date_based.archive_year',
dict(info_dict)),
# Day summary view used by calendar
(r'^reports/archive/(?P<year>\d{4})/(?P<month>\d{1,2})/(?P<day>\d{1,2})/$',
'django.views.generic.date_based.archive_day',
dict(info_dict, template_name='tests/testresult_archive_day.html',
month_format='%m')),
# etc...
)
We don't have much static media or traffic (10s of hits per day or
something like that), so we didn't see much of an issue having Django
just handle the static serving. Even these generic views are grinding
for many seconds before producing the results. We tried using
mod_python in Apache to see if that would help, but no dice it was
just as slow. Turning off debugging also didn't help any it was
equally slow. So are we doing anything here that's particularly
inefficient? If so, what can we do better? I'd be glad to provide
other info if necessary. Thanks!
-peter
--
Peter M Aarestad
[EMAIL PROTECTED]
During times of universal deceit, telling the truth becomes a revolutionary act.
--George Orwell
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
