On 1/4/07, David Abrahams <[EMAIL PROTECTED]> wrote: ...
If I log into the server and run "top" while trying to access pages, I don't see any alarming jumps in CPU load; the hungriest processes typically stay in single-digit (or below) percentages of CPU usage, so I doubt profiling is going to be much use. I don't really know where to start in debugging this.
Most likely, KeepAlive is holding processes unavailable while sitting idle. Next most likely is # of child processes. Try fiddling with Min and MaxSpareServers. http://httpd.apache.org/docs/2.0/mod/prefork.html Next most likely is that you're serving media and django on the save httpd. More suggestions: http://www.jacobian.org/writing/2005/dec/12/django-performance-tips/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
