yezooz napisał(a): >>> two words: intelligent caching >>> Know what you're asking for commonly, and cache it up with memcache. >>> That will do you a world of benefit. >> Well of course caching will solve some of the problems, but cache >> still needs to regenerated sometime... > > I should say that I'm thinking about few millions of pageviews a day
Memcached is designed to handle such traffic, so use it intelligently. I mean, don't rely only on page/view caching provided with Django out of the box, use queryset result and object cache. With reasonable expiration time, your db will be queried rarely and you'd get your objects nearly instantly. The other things worth putting in cache are computed values -- if you don't mind some delays. We do such things and the only thing I can say is that it just works, we are able to handle many thousands of requests per minute and the sites are much more responsible. Unfortunately, that approach would require deleting the objects from cache everytime they are modified, but it's a fair tradeoff IMO. -- Jarek Zgoda Skype: jzgoda | GTalk: [EMAIL PROTECTED] | voice: +48228430101 "We read Knuth so you don't have to." (Tim Peters) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
