On Tuesday, February 18, 2014 6:02:59 PM UTC-5, Graham Dumpleton wrote:
It is generally always better to start a new discussion thread.
Roger.
Your path doesn't quite make sense. Why are you adding the path to the
WSGI script file to python-path? Do you mean to have used:
Oops.
I've
This question started on SO:
http://serverfault.com/questions/576527/apache-processes-in-top-more-than-maxclients/576600
I've updated my Apache config and mod_wsgi settings, but am still
experiencing memory creep. Here's my site conf and my apache2.conf:
WSGIDaemonProcess mywsgi user=www-data
I just changed processes=2 threads=5 to see how long I can stay alive
without queuing requests. htop now reports 18 threads:
10320 www-data 20 0 172M 75264 4668 S 0.0 0.9 0:57.46 mod-wsgi
-k start
10321 www-data 20 0 172M 75264 4668 S 0.0 0.9 1:16.62 mod-wsgi
Hi everyone.
I'm using a big server to run my site and I'm having issues when trying to
do some performance tests in the server.
Here are the specs of the server:
Ubuntu 12.04.3 x64 3.2.0-55-virtual
60GB RAM
Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz (16 cores)
*Python 2.7.3*
I left the config processes=2 threads=5 from about 12:00pm ET - 1:40pm ET
and the capacity analysis and app reports showed lots of request queueing
and really, really bad performance. During that time apache memory usage
climbed from 140M-180M in NR's server monitor. Going to try flipping
Just discovered htop tree view. With processes=5 threads=2 I wouldn't
expect to see 5 threads under each process. Memory for one of these
processes has ballooned to 283M. Eventually when all 5 of them get there,
that means I'll be using 1.5G of ram for mod_wsgi.
20179 www-data 20 0 147M
After monitoring the wsgi processes for some time I noticed one of the
processes consumed 585M of memory. Ouch. if all 5 processes consumed that
much, the server would be approaching 3G of memory used by mod_wsgi. After
looking through the mod_wsgi config parameters
Graham, I'm still not sure why with processes=5 threads=2 I see 5 threads
for each process for mod_wsgi in htop. If you could explain that last
little hanging chad it would be great. Thanks!
Updated SO with summary of
solution:
Can you please provide the rest of your mod_wsgi configuration.
You do not show what you have set for WSGIDaemonProcess, nor enough about the
structure of stuff in your VirtualHost to validate that things are set up
correct to delegate requests to that daemon process group.
For the Apache
Sorry, I have been working in that.
I have two VirtualHosts.
VirtualHost *:443
SSLEngine On
SSLCompression Off
SSLProtocol +TLSv1 +SSLv3
SSLHonorCipherOrder On
SSLCipherSuite
ECDHE-RSA-AES128-SHA256:AES128-GCM-SHA256:HIGH:!MD5:!aNULL:!EDH
SSLCertificateFile
Blog version of the issue with number of threads seen.
http://blog.dscpl.com.au/2014/02/use-of-threading-in-modwsgi-daemon-mode.html
I stole your htop output. :-)
Note that the blog post explains a bit more, mentioning a transient reaper
thread that is created at the time of shutdown.
It is
Thank you, Graham. This information is invaluable.
Mark
On Wednesday, February 19, 2014 12:05:56 PM UTC-5, scoopseven wrote:
This question started on SO:
http://serverfault.com/questions/576527/apache-processes-in-top-more-than-maxclients/576600
I've updated my Apache config and mod_wsgi
12 matches
Mail list logo
