Without knowing a hell of a lot more of the details of you site, what you're trying to do, etc - nobody can reasonably answer this question. The ORM is fine, but if it's not as fast as you need for certain queries, you can always drop back to RAW sql to see if that will give you speed. At the level of activity you're citing, you'll have to make some serious choices between how personalized you'd like the site and how much resource you can throw at the problem.
Between caching, profiling, and having a good sense of what your current hardware can run to, you can scale out Django horizontally to achieve the scale you need. -joe On 9/18/07, yezooz <[EMAIL PROTECTED]> wrote: > > > > On Sep 18, 10:23 pm, yezooz <[EMAIL PROTECTED]> wrote: > > On Sep 18, 10:14 pm, "Joseph Heck" <[EMAIL PROTECTED]> wrote: > > > > > 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 > > > > > > > > > > -joe > > > > > On 9/18/07, yezooz <[EMAIL PROTECTED]> wrote: > > > > > > hi all, > > > > > > I'm sure many of you run high traffic websites in Django and I'm very > > > > curious how you're avoiding performance hit caused by built-in ORM. > > > > Select_related not always working and it's still might generate dozens > > > > of select's. > > > > Are you just running custom SQL queries with joins ? > > > > > > greetings > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
