On Dec 11, 2007 1:39 PM, Richard Coleman <[EMAIL PROTECTED]> wrote: ... > > > I think a large part of my question really comes down to "Is 300 > requests per second reasonable for an uncached django site on a single > machine?". Maybe it is. > > We are looking at using the memcached API in our code, and I'm sure we > will get a speedup there. But before we start down that route, I wanted > to make sure we weren't doing any silly on the raw site. > > I think my next step is to use the profiler and find out why the site is > so CPU intensive. > > Thanks for all the help.
Again I suggest a hello-world view as a baseline, but if you really are doing 7000 queries per second, perhaps you're also constructing a lot of ORM objects; there's some overhead to the signalling (pre/post init, pre/post save). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
