On 15 oct, 15:19, David Reynolds <[EMAIL PROTECTED]> wrote:
> On 15 Oct 2008, at 1:00 pm, bruno desthuilliers wrote:
>
> > Did you profile to spot where the bottleneck really is? Not tested but
> > here are a couple links on the topic:
> >http://www.djangosnippets.org/snippets/186/
> >http://code.djangoproject.com/wiki/ProfilingDjango
>
> I've been trying the profiling middleware and can't seem to get any
> results out for the view I'm testing - it keeps timing out (it works
> for other views on this site).
Can't help much on this, sorry :(
> > Also and out of curiousity, is there a reason you didn't use the csv
> > module solution ?
> >http://docs.djangoproject.com/en/dev/howto/outputting-csv/#using-
> > the-python-csv-library
>
> I think I thought I'd be able to make a more flexible output - I may
> have been wrong. Do you think the csv module would be quicker?
I could be (and I strongly suspect it would be), but I really can't
tell for sure. Now this should be easy to find out, isn't it ?-)
There are also a couple micro-optimization tricks, like correct use of
select_related, aliasing of frequently accessed attributes and methods
outside a loop, etc, - so we could eventually help a bit if you post
your code - but anyway : unless you do something very obviously wrong
in your view, trying to optimize without first profiling is usually
(from experience) a waste of time.
You could at least benchmark the view code *without* the template
rendering to find out weither the main bottleneck is in the view code
itself or in the template.
Sorry, nothing better.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
