> Between caching, profiling, and having a good sense of what your Profiling...the #1 thing to do.
Without profiling the app under "normal usage" (common actions & browsing patterns gleaned from the current deployment) scaled to high loads, you're just twiddling knobs and wasting time. If the problem is in the queries, page-caching isn't going to help. If each individual query is fine, but you have too many of them, caching database queries may help. If it's bad python code, DB caching and twiddling your queries isn't going to save you either. Until you know _where_ the problem resides, you can't fix it. And it's also good to profile under load in a testing lab, rather than waiting for real-world load to drag your production machine(s) to their knees :) -tim --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
