Joseph raises a good point.  I only recently discovered what a
performance killer DEBUG mode can be when it comes to queries.  It
will cause your client machine (the web server in this case) to run
out of memory after a lengthy process (such as data loading).  Are you
profiling in DEBUG mode?

On Dec 11, 1:54 pm, "Joseph Heck" <[EMAIL PROTECTED]> wrote:
> Definitely take that specific dynamic page and profile it - see what's
> happening and why its slow. That's clearly your first bottleneck to
> work on from the data you've provided.
>
> There's a wiki page on that very process 
> here:http://code.djangoproject.com/wiki/ProfilingDjangoand there's
> additionally some information you can get when you enable DEBUG to see
> how long the SQL queries are taking for that dynamic page. There's a
> nice snippet to help there athttp://www.djangosnippets.org/snippets/93/
>
> -joe
>
> On Dec 11, 2007 10:49 AM, Richard Coleman <[EMAIL PROTECTED]> wrote:
>
>
>
> > Brian Morton wrote:
> > > Are you serving static content from the same apache instance?  Also,
> > > what kind of network connectivity do you have between your web and
> > > mysql servers?  It sounds like apache might need some tuning in terms
> > > of thread parameters.  Have you enabled caching yet?  Turn on the
> > > cache framework site-wide and set your expiration period to 1 minute
> > > or something like that.  You can go back and only enable it for views
> > > that you want cached later.
>
> > 1. Static content and dynamic are on the same server (that will change
> > on production).  But they are on different apache virtual.  Mod_python
> > is turned off for the static stuff.  Hitting only a static page is very
> > fast (6500 requests per second).  Hitting the dynamic side is slow (300
> > requests per second).
>
> > 2. It's gigE between the web server and mysql server, on a dedicated
> > switch.  The database is working pretty hard (7000 selects per second),
> > but doesn't seem to be the bottleneck.  The webserver is hammered
> > (typing any command takes a long time).
> > 3. I'm using prefork MPM on apache with maxclients set to 1000.
>
> > We are starting to experiment with caching, but I want to improve the
> > raw performance of the site as well.
>
> > Richard Coleman
> > [EMAIL PROTECTED]
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to