On 7/2/07, jj <[EMAIL PROTECTED]> wrote: > > I have an app which handles, lets say, Books. I'd like to display up > to 1,000 of them on a single page.
How many HTTP requests? How many queries? How many bytes in response? What web server? ... > - Books have Authors, Publishers, etc. I use select_related() instead > of all(), but this does not improve performance much (half a second > over about 6 seconds query time). I think you're not measuring the whole thing somewhere-- or there's a bug in select_related. ... > - Platforms are WinXP. Not to be facetious, but this may be part of the problem. > - I user memcache/Win32, initial request is slow, subsequent requests > are faster, Err, does this mean subsequents are cache hits, or that the memcache client is slow at connecting, or something else? > - Each user can only see books which they have borrowed in the past or > who's technical area is theirs. So there's an extra query to filter > down the initial list of all books to the one they are actually > authorized to see. So you're caching the whole initial list and then filtering later? Or you're caching the individual lists? Or something else? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
