Re: Performance of a django website

have you tried mod_wsgi ?

Nic пишет:
> "Karen Tracey" <kmtraceygmail.com> writes:
> 
>> On Dec 11, 2007 1:49 PM, Richard Coleman
<rcolemancriticalmagic.com> wrote:
>>
>>> 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).
>>>
>> DB handling 7000 selects/sec while web server is
serving 300 pages/sec
>> implies each page request is generating >20
select requests.  Does that seem
>> reasonable to you based on the content of the page
you are serving?  (It
>> seems high to me.)  Brian Morton provided a pointer
to the doc for
>> select_related, which could help to reduce the
number of selects.  Even if
>> the database is keeping up, so many round-trips
talking to it for a single
>> page request is going to add up.
> 
> 
> Have you tried a connection pool?
> 
> 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at htt
p://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---