On Dec 11, 8:39 pm, Richard Coleman <[EMAIL PROTECTED]>
wrote:
> Forest Bond wrote:
> >>> - How are you running your Django app? Mod_python? FastCGI?
> >>> - What web server are you using?
> >>> - What's the nature of the dynamic Django request you are measuring?
> >>> How many DB queries does i
On Dec 26, 6:44 pm, Dima Dogadaylo <[EMAIL PROTECTED]> wrote:
> On Dec 11, 8:37 pm, Richard Coleman <[EMAIL PROTECTED]>
> wrote:
>
> > 1. mod_python
> > 2. apache 2.2.4
> > 3. I'm using funkload and ab to measure the requests per second of one
> > of the base pages within the dynamic part of the w
On Dec 11, 8:37 pm, Richard Coleman <[EMAIL PROTECTED]>
wrote:
> 1. mod_python
> 2. apache 2.2.4
> 3. I'm using funkload and ab to measure the requests per second of one
> of the base pages within the dynamic part of the website
> 4. When I hit a static page in the same way (using ab), I get 650
have you tried mod_wsgi ?
Nic пишет:
> "Karen Tracey" <[EMAIL PROTECTED]> writes:
>
>> On Dec 11, 2007 1:49 PM, Richard Coleman <[EMAIL PROTECTED]> wrote:
>>
>>> 1. Static content and dynamic are on the same server (that will change
>>> on production). But they are on different apache virtual.
Whats really interesting in this discussion is that there are no words
about the django application it self have you coded your
application in a django effencient way?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Group
"Karen Tracey" <[EMAIL PROTECTED]> writes:
> On Dec 11, 2007 1:49 PM, Richard Coleman <[EMAIL PROTECTED]> 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 st
On Dec 12, 6:21 am, Rajesh Dhawan <[EMAIL PROTECTED]> wrote:
> Hi again,
>
> > 3. I'm using prefork MPM on apache with maxclients set to 1000.
>
> Apart from Joe's excellent profiling suggestion, I would recommend
> reducing maxclients to a much lower value (like say 100) and then
> increasing it
On Dec 11, 2007 1:28 PM, Richard Coleman <[EMAIL PROTECTED]> wrote:
> I have maxclients set to 1000, but the number of apache processes never
> gets close to that value. I've played around with various settings for
> maxclient, but as long as I don't set it too low, this never comes into
> play.
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 co
On Dec 11, 2007 1:49 PM, Richard Coleman <[EMAIL PROTECTED]> 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 (65
Forest Bond wrote:
>>> - How are you running your Django app? Mod_python? FastCGI?
>>> - What web server are you using?
>>> - What's the nature of the dynamic Django request you are measuring?
>>> How many DB queries does it make? Is DEBUG mode off?
>>> - What kind of numbers do you get when you s
On Dec 11, 2007 1:21 PM, Rajesh Dhawan <[EMAIL PROTECTED]> wrote:
>
> Hi again,
>
> > 3. I'm using prefork MPM on apache with maxclients set to 1000.
>
> Apart from Joe's excellent profiling suggestion, I would recommend
> reducing maxclients to a much lower value (like say 100) and then
> increas
Rajesh Dhawan wrote:
>> 3. I'm using prefork MPM on apache with maxclients set to 1000.
>>
>
> Apart from Joe's excellent profiling suggestion, I would recommend
> reducing maxclients to a much lower value (like say 100) and then
> increasing it gradually.
>
> From your description of the slu
Hi,
On Tue, Dec 11, 2007 at 01:37:36PM -0500, Richard Coleman wrote:
> Rajesh Dhawan wrote:
> >> When I stress test the dynamic part of the site, I am only getting about
> >> 300 requests per second on my test setup. This is using two Dell 1950's
> >> (one for web, one for mysql database). These
http://www.djangoproject.com/documentation/db-api/#select-related
On Dec 11, 1:18 pm, Joe <[EMAIL PROTECTED]> wrote:
> I've found the largest memory hog to be the native way related tables
> are setup.
>
> Check class definitions with related tables and edit as such:
>
> class ...(models.Mode):
>
Hi again,
> 3. I'm using prefork MPM on apache with maxclients set to 1000.
Apart from Joe's excellent profiling suggestion, I would recommend
reducing maxclients to a much lower value (like say 100) and then
increasing it gradually.
>From your description of the sluggish response of your web s
Sorry, just saw your earlier post about debug being turned off. I
would say it is definitely time to start profiling your code.
On Dec 11, 2:11 pm, Brian Morton <[EMAIL PROTECTED]> wrote:
> Joseph raises a good point. I only recently discovered what a
> performance killer DEBUG mode can be when
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
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/ProfilingDjango and there's
additiona
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 th
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
If you don't already use them:
Firebug:
http://www.getfirebug.com/
will show you how long each component of the page takes from request to
response and shows you what components are returned in parallel (among
other really cool features). This can help identify your bottleneck.
For example, i
Richard Coleman wrote:
> Rajesh Dhawan wrote:
>
>>> When I stress test the dynamic part of the site, I am only getting about
>>> 300 requests per second on my test setup. This is using two Dell 1950's
>>> (one for web, one for mysql database). These are very powerful machines
>>> (3.0ghz Xeon
Rajesh Dhawan wrote:
>> When I stress test the dynamic part of the site, I am only getting about
>> 300 requests per second on my test setup. This is using two Dell 1950's
>> (one for web, one for mysql database). These are very powerful machines
>> (3.0ghz Xeons, 8 cores each, 16 gig of ram, 15
On Dec 11, 2007 12:18 PM, Joe <[EMAIL PROTECTED]> wrote:
>
> I've found the largest memory hog to be the native way related tables
> are setup.
>
> Check class definitions with related tables and edit as such:
>
> class ...(models.Mode):
> relatedtable= models.ForeignKey(RelatedTable, core=Tru
I've found the largest memory hog to be the native way related tables
are setup.
Check class definitions with related tables and edit as such:
class ...(models.Mode):
relatedtable= models.ForeignKey(RelatedTable, core=True,
raw_id_admin=True)
The raw_id_admin=True prevents django from pulli
Add on to Rajesh's list -
what pages are you requesting and have you profiled them to understand
what's taking long?
-joe
On Dec 11, 2007 10:08 AM, Rajesh Dhawan <[EMAIL PROTECTED]> wrote:
>
> Hi Richard,
>
> >
> > When I stress test the dynamic part of the site, I am only getting about
> > 300
Hi Richard,
>
> When I stress test the dynamic part of the site, I am only getting about
> 300 requests per second on my test setup. This is using two Dell 1950's
> (one for web, one for mysql database). These are very powerful machines
> (3.0ghz Xeons, 8 cores each, 16 gig of ram, 15k SAS driv
I think that some info about your web-server could be important.
--~--~-~--~~~---~--~~
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
At work, we are developing a commercial website based on Django. It's a
fairly dynamic site (think social networking). I am doing the initial
load testing to estimate the number of servers we will need for the
production site. The production site will be load balanced using a pair
of BigIP
30 matches
Mail list logo
