On Wed, 05 May 2010 02:49:27 +0200, Graham Dumpleton
<[email protected]> wrote:
[...]So, look at database query times and improving them. Look at
caching,
be that in the application using memcached or in front end web server
caches. Do everything possible to avoid doing the stuff that takes a
long time and you will get a much better results as far as request
capacity.
Thanks for both of your answers! The reason why I've been talking about
processes and threads is that this is the only configuration setting where
I have to guess. And according to the documentation I have to make a good
guess because the number of processes and threads is fixed and doesn't
increase if demand grows. That's why I think it would be great if mod_wsgi
would provide a number to easily measure something like load average
(compare to 'cat /proc/loadavg' to get the load average of a Linux
server). Does it make sense? I wonder because I find it a bit strange that
I have to guess but mod_wsgi doesn't help me to find out if my guess makes
sense? Or am I giving too much weight to this configuration setting (then
some sensible default values in mod_wsgi would make sense so you don't
need to bother at all)?
Boris
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en.
