[modwsgi] Re: mod_wsgi Showing more threads in htop than assigned
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
-k start
10325 www-data 20 0 172M 75264 4668 S 0.0 0.9 0:03.43 mod-wsgi
-k start
10318 www-data 20 0 172M 75264 4668 S 42.0 0.9 1:13.23 mod-wsgi
-k start
10306 www-data 20 0 172M 75264 4668 S 44.0 0.9 6:04.31 mod-wsgi
-k start
10315 www-data 20 0 172M 75264 4668 S 0.0 0.9 0:00.00 mod-wsgi
-k start
10317 www-data 20 0 172M 75264 4668 S 0.0 0.9 1:12.87 mod-wsgi
-k start
10316 www-data 20 0 172M 75264 4668 S 0.0 0.9 0:00.13 mod-wsgi
-k start
10319 www-data 20 0 172M 75264 4668 S 0.0 0.9 1:14.81 mod-wsgi
-k start
10345 www-data 20 0 166M 70584 4988 S 0.0 0.9 0:03.41 mod-wsgi
-k start
10322 www-data 20 0 166M 70584 4988 S 0.0 0.9 0:00.00 mod-wsgi
-k start
10323 www-data 20 0 166M 70584 4988 S 0.0 0.9 0:00.14 mod-wsgi
-k start
10324 www-data 20 0 166M 70584 4988 S 0.0 0.9 1:04.75 mod-wsgi
-k start
10327 www-data 20 0 166M 70584 4988 S 31.0 0.9 1:03.30 mod-wsgi
-k start
10305 www-data 20 0 166M 70584 4988 S 66.0 0.9 5:30.12 mod-wsgi
-k start
10326 www-data 20 0 166M 70584 4988 S 0.0 0.9 1:06.65 mod-wsgi
-k start
10328 www-data 20 0 166M 70584 4988 S 16.0 0.9 1:05.57 mod-wsgi
-k start
10329 www-data 20 0 166M 70584 4988 S 19.0 0.9 1:01.67 mod-wsgi
-k start
So it looks like htop is reporting 9 threads per process, still 3 more than
the 6 I would expect (1 process + 5 threads).
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 settings, but am still
experiencing memory creep. Here's my site conf and my apache2.conf:
WSGIDaemonProcess mywsgi user=www-data group=www-data processes=5
threads=5 display-name=mod-wsgi
python-path=/home/admin/.virtualenvs/django/lib/python2.7/site-packages
WSGIPythonHome /home/admin/.virtualenvs/django
WSGIRestrictEmbedded On
WSGILazyInitialization On
VirtualHost 127.0.0.1:8080
ServerName www.mysite.com
DocumentRoot /srv/mysite
SetEnvIf X-Forwarded-Protocol https HTTPS=1
WSGIScriptAlias / /srv/mysite/system/apache/django.wsgi
process-group= mywsgi application-group=%{GLOBAL}
RequestHeader add X-Queue-Start %t
/VirtualHost
IfModule mpm_worker_module
StartServers 1
ThreadsPerChild 5
MinSpareThreads 5
MaxSpareThreads 10
MaxClients 25
ServerLimit 5
MaxRequestsPerChild 0
MaxMemFree1024
/IfModule
I'm watching apache and mod_wsgi via htop and apache seems to be playing
by the rules, never loading more than 25 threads. It usually stays around
10-15 threads. We average around 5-6 requests/second monitored by
/server-status/. The thing that's bothering me is that I'm counting 44
mod_wsgi threads in htop. I assumed that since I had processes=5 threads=5
I would only see a maximum of 30 threads below (5 processes + 25 threads).
Partial htop dump:
2249 www-data 20 0 159M 65544 4676 S 26.0 0.8 2:09.93 mod-wsgi
-k start
2248 www-data 20 0 164M 69040 5560 S 148. 0.8 2:10.72 mod-wsgi
-k start
2274 www-data 20 0 159M 65544 4676 S 0.0 0.8 0:12.58 mod-wsgi
-k start
2250 www-data 20 0 157M 62212 5168 S 10.0 0.7 1:50.35 mod-wsgi
-k start
2291 www-data 20 0 164M 69040 5560 S 41.0 0.8 0:17.07 mod-wsgi
-k start
2251 www-data 20 0 165M 69320 4676 S 0.0 0.8 1:59.48 mod-wsgi
-k start
2272 www-data 20 0 159M 65544 4676 S 0.0 0.8 0:28.67 mod-wsgi
-k start
2282 www-data 20 0 165M 69320 4676 S 0.0 0.8 0:33.85 mod-wsgi
-k start
2292 www-data 20 0 164M 69040 5560 S 28.0 0.8 0:28.08 mod-wsgi
-k start
2298 www-data 20 0 157M 62212 5168 S 0.0 0.7 0:14.93 mod-wsgi
-k start
2299 www-data 20 0 157M 62212 5168 S 1.0 0.7 0:23.71 mod-wsgi
-k start
2358 www-data 20 0 164M 69040 5560 S 1.0 0.8 0:02.62 mod-wsgi
-k start
2252 www-data 20 0 165M 70468 4660 S 41.0 0.8 1:55.85 mod-wsgi
-k start
2273 www-data 20 0 159M 65544 4676 S 10.0 0.8 0:29.03 mod-wsgi
-k start
2278 www-data 20 0 159M 65544 4676 S 1.0 0.8 0:02.79 mod-wsgi
-k start
2264 www-data 20 0
[modwsgi] Re: mod_wsgi Showing more threads in htop than assigned
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
processes/threads around. Setting processes=5 threads=2 at 1:40pm ET.
Request queuing immediately stopped and after the apache restart apache
reports 300MB of memory usage. htop reports 30 threads. It looks like each
process has 6 threads, when sorting by VIRT, they're all grouped together.
There are 5 groups of 6, so I'm not sure how threads=2 is controlling
anything. Each process looks like it's consuming 130M-160M of memory. Not
sure why these processes don't show up on the NR server monitor report as
mod_wsgi, or why I can't differentiate them from apache2
(https://rpm.newrelic.com/accounts/67402/servers/113/processes#id=152494639).
PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command
20212 www-data 20 0 136M 64604 4664 S 0.0 0.8 0:00.00 mod-wsgi
-k start
20213 www-data 20 0 136M 64604 4664 S 0.0 0.8 0:00.14 mod-wsgi
-k start
20214 www-data 20 0 136M 64604 4664 S 51.0 0.8 1:14.28 mod-wsgi
-k start
20215 www-data 20 0 136M 64604 4664 S 33.0 0.8 1:18.60 mod-wsgi
-k start
20240 www-data 20 0 136M 64604 4664 S 1.0 0.8 0:03.85 mod-wsgi
-k start
20179 www-data 20 0 136M 64604 4664 S 86.0 0.8 2:39.99 mod-wsgi
-k start
20203 www-data 20 0 131M 61340 4672 S 0.0 0.7 0:00.00 mod-wsgi
-k start
20204 www-data 20 0 131M 61340 4672 S 0.0 0.7 0:00.26 mod-wsgi
-k start
20205 www-data 20 0 131M 61340 4672 S 19.0 0.7 1:21.73 mod-wsgi
-k start
20206 www-data 20 0 131M 61340 4672 S 26.0 0.7 1:23.35 mod-wsgi
-k start
20207 www-data 20 0 131M 61340 4672 S 0.0 0.7 0:04.20 mod-wsgi
-k start
20177 www-data 20 0 131M 61340 4672 S 46.0 0.7 2:52.40 mod-wsgi
-k start
20196 www-data 20 0 131M 59552 4668 S 0.0 0.7 0:00.00 mod-wsgi
-k start
20197 www-data 20 0 131M 59552 4668 S 0.0 0.7 0:00.16 mod-wsgi
-k start
20198 www-data 20 0 131M 59552 4668 S 13.0 0.7 1:16.92 mod-wsgi
-k start
20199 www-data 20 0 131M 59552 4668 S 16.0 0.7 1:14.32 mod-wsgi
-k start
20200 www-data 20 0 131M 59552 4668 S 0.0 0.7 0:03.91 mod-wsgi
-k start
20175 www-data 20 0 131M 59552 4668 S 30.0 0.7 2:38.28 mod-wsgi
-k start
20227 www-data 20 0 130M 60680 4664 S 0.0 0.7 0:00.00 mod-wsgi
-k start
20228 www-data 20 0 130M 60680 4664 S 0.0 0.7 0:00.22 mod-wsgi
-k start
20229 www-data 20 0 130M 60680 4664 S 14.0 0.7 1:22.35 mod-wsgi
-k start
20230 www-data 20 0 130M 60680 4664 S 12.0 0.7 1:23.82 mod-wsgi
-k start
20241 www-data 20 0 130M 60680 4664 S 0.0 0.7 0:04.09 mod-wsgi
-k start
20178 www-data 20 0 130M 60680 4664 S 28.0 0.7 2:53.50 mod-wsgi
-k start
20188 www-data 20 0 132M 61232 4672 S 0.0 0.7 0:00.00 mod-wsgi
-k start
20189 www-data 20 0 132M 61232 4672 S 0.0 0.7 0:00.17 mod-wsgi
-k start
20190 www-data 20 0 132M 61232 4672 S 45.0 0.7 1:14.18 mod-wsgi
-k start
20191 www-data 20 0 132M 61232 4672 S 75.0 0.7 1:25.57 mod-wsgi
-k start
20192 www-data 20 0 132M 61232 4672 S 1.0 0.7 0:04.33 mod-wsgi
-k start
20176 www-data 20 0 132M 61232 4672 S 122. 0.7 2:47.90 mod-wsgi
-k start
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 settings, but am still
experiencing memory creep. Here's my site conf and my apache2.conf:
WSGIDaemonProcess mywsgi user=www-data group=www-data processes=5
threads=5 display-name=mod-wsgi
python-path=/home/admin/.virtualenvs/django/lib/python2.7/site-packages
WSGIPythonHome /home/admin/.virtualenvs/django
WSGIRestrictEmbedded On
WSGILazyInitialization On
VirtualHost 127.0.0.1:8080
ServerName www.mysite.com
DocumentRoot /srv/mysite
SetEnvIf X-Forwarded-Protocol https HTTPS=1
WSGIScriptAlias / /srv/mysite/system/apache/django.wsgi
process-group= mywsgi application-group=%{GLOBAL}
RequestHeader add X-Queue-Start %t
/VirtualHost
IfModule mpm_worker_module
StartServers 1
ThreadsPerChild 5
MinSpareThreads 5
MaxSpareThreads 10
MaxClients 25
ServerLimit 5
MaxRequestsPerChild 0
MaxMemFree1024
/IfModule
I'm watching apache and
[modwsgi] Re: mod_wsgi Showing more threads in htop than assigned
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 76408 5680 S 28.0 0.9 10:17.85 │ ├─
mod-wsgi -k start
20240 www-data 20 0 147M 76408 5680 S 1.0 0.9 0:14.99 │ │ ├─
mod-wsgi -k start
20215 www-data 20 0 147M 76408 5680 S 12.0 0.9 5:05.16 │ │ ├─
mod-wsgi -k start
20214 www-data 20 0 147M 76408 5680 S 14.0 0.9 4:53.99 │ │ ├─
mod-wsgi -k start
20213 www-data 20 0 147M 76408 5680 S 0.0 0.9 0:00.63 │ │ ├─
mod-wsgi -k start
20212 www-data 20 0 147M 76408 5680 S 0.0 0.9 0:00.00 │ │ └─
mod-wsgi -k start
20178 www-data 20 0 138M 67680 5212 S 52.0 0.8 11:01.62 │ ├─
mod-wsgi -k start
20241 www-data 20 0 138M 67680 5212 S 0.0 0.8 0:15.45 │ │ ├─
mod-wsgi -k start
20230 www-data 20 0 138M 67680 5212 S 15.0 0.8 5:17.81 │ │ ├─
mod-wsgi -k start
20229 www-data 20 0 138M 67680 5212 S 35.0 0.8 5:24.63 │ │ ├─
mod-wsgi -k start
20228 www-data 20 0 138M 67680 5212 S 0.0 0.8 0:00.71 │ │ ├─
mod-wsgi -k start
20227 www-data 20 0 138M 67680 5212 S 0.0 0.8 0:00.00 │ │ └─
mod-wsgi -k start
20177 www-data 20 0 137M 67764 5428 S 7.0 0.8 10:47.27 │ ├─
mod-wsgi -k start
20207 www-data 20 0 137M 67764 5428 S 0.0 0.8 0:15.18 │ │ ├─
mod-wsgi -k start
20206 www-data 20 0 137M 67764 5428 S 7.0 0.8 5:16.82 │ │ ├─
mod-wsgi -k start
20205 www-data 20 0 137M 67764 5428 S 0.0 0.8 5:11.55 │ │ ├─
mod-wsgi -k start
20204 www-data 20 0 137M 67764 5428 S 0.0 0.8 0:00.69 │ │ ├─
mod-wsgi -k start
20203 www-data 20 0 137M 67764 5428 S 0.0 0.8 0:00.00 │ │ └─
mod-wsgi -k start
20176 www-data 20 0 138M 68144 5004 S 48.0 0.8 10:47.64 │ ├─
mod-wsgi -k start
20192 www-data 20 0 138M 68144 5004 S 1.0 0.8 0:15.62 │ │ ├─
mod-wsgi -k start
20191 www-data 20 0 138M 68144 5004 S 15.0 0.8 5:25.78 │ │ ├─
mod-wsgi -k start
20190 www-data 20 0 138M 68144 5004 S 31.0 0.8 5:02.00 │ │ ├─
mod-wsgi -k start
20189 www-data 20 0 138M 68144 5004 S 0.0 0.8 0:00.60 │ │ ├─
mod-wsgi -k start
20188 www-data 20 0 138M 68144 5004 S 0.0 0.8 0:00.00 │ │ └─
mod-wsgi -k start
20175 www-data 20 0 283M 197M 5540 S 72.0 2.4 12:24.34 │ └─
mod-wsgi -k start
20200 www-data 20 0 283M 197M 5540 S 0.0 2.4 0:14.62 │ ├─
mod-wsgi -k start
20199 www-data 20 0 283M 197M 5540 S 22.0 2.4 5:25.50 │ ├─
mod-wsgi -k start
20198 www-data 20 0 283M 197M 5540 S 50.0 2.4 6:40.60 │ ├─
mod-wsgi -k start
20197 www-data 20 0 283M 197M 5540 S 0.0 2.4 0:00.69 │ ├─
mod-wsgi -k start
20196 www-data 20 0 283M 197M 5540 S 0.0 2.4 0:00.00 │ └─
mod-wsgi -k start
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 settings, but am still
experiencing memory creep. Here's my site conf and my apache2.conf:
WSGIDaemonProcess mywsgi user=www-data group=www-data processes=5
threads=5 display-name=mod-wsgi
python-path=/home/admin/.virtualenvs/django/lib/python2.7/site-packages
WSGIPythonHome /home/admin/.virtualenvs/django
WSGIRestrictEmbedded On
WSGILazyInitialization On
VirtualHost 127.0.0.1:8080
ServerName www.mysite.com
DocumentRoot /srv/mysite
SetEnvIf X-Forwarded-Protocol https HTTPS=1
WSGIScriptAlias / /srv/mysite/system/apache/django.wsgi
process-group= mywsgi application-group=%{GLOBAL}
RequestHeader add X-Queue-Start %t
/VirtualHost
IfModule mpm_worker_module
StartServers 1
ThreadsPerChild 5
MinSpareThreads 5
MaxSpareThreads 10
MaxClients 25
ServerLimit 5
MaxRequestsPerChild 0
MaxMemFree1024
/IfModule
I'm watching apache and mod_wsgi via htop and apache seems to be playing
by the rules, never loading more than 25 threads. It usually stays around
10-15 threads. We average around 5-6 requests/second monitored by
/server-status/. The thing that's bothering me is that I'm counting 44
mod_wsgi threads in htop. I assumed that since I had processes=5 threads=5
I would only see a maximum of 30 threads below (5 processes + 25 threads).
Partial htop dump:
2249 www-data 20 0 159M 65544 4676 S 26.0 0.8
[modwsgi] Re: mod_wsgi Showing more threads in htop than assigned
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
(https://code.google.com/p/modwsgi/wiki/ConfigurationDirectives) I
discovered *maximum-requests *and *inactivity-timeout. *I added these
parameters to my mod_wsgi directive now looks like this:
WSGIDaemonProcess mywsgi user=www-data group=www-data processes=5 threads=2
inactivity-timeout=300 maximum-requests=200 display-name=mod-wsgi
python-path=/home/admin/.virtualenvs/django/lib/python2.7/site-packages
Now, no matter how much memory my app makes mod_wsgi consume, the processes
are restarted after 5 minutes of inactivity or 200 requests. I'll probably
play with that number so that processes aren't being restarted all of the
time but I can maintain a consistent memory footprint. In any case, the
problem is solved. My app has a massive footprint (at least one django view
does) but now I'm able to control it by recycling mod_wsgi processes. Hope
this helps someone else out there.
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 settings, but am still
experiencing memory creep. Here's my site conf and my apache2.conf:
WSGIDaemonProcess mywsgi user=www-data group=www-data processes=5
threads=5 display-name=mod-wsgi
python-path=/home/admin/.virtualenvs/django/lib/python2.7/site-packages
WSGIPythonHome /home/admin/.virtualenvs/django
WSGIRestrictEmbedded On
WSGILazyInitialization On
VirtualHost 127.0.0.1:8080
ServerName www.mysite.com
DocumentRoot /srv/mysite
SetEnvIf X-Forwarded-Protocol https HTTPS=1
WSGIScriptAlias / /srv/mysite/system/apache/django.wsgi
process-group= mywsgi application-group=%{GLOBAL}
RequestHeader add X-Queue-Start %t
/VirtualHost
IfModule mpm_worker_module
StartServers 1
ThreadsPerChild 5
MinSpareThreads 5
MaxSpareThreads 10
MaxClients 25
ServerLimit 5
MaxRequestsPerChild 0
MaxMemFree1024
/IfModule
I'm watching apache and mod_wsgi via htop and apache seems to be playing
by the rules, never loading more than 25 threads. It usually stays around
10-15 threads. We average around 5-6 requests/second monitored by
/server-status/. The thing that's bothering me is that I'm counting 44
mod_wsgi threads in htop. I assumed that since I had processes=5 threads=5
I would only see a maximum of 30 threads below (5 processes + 25 threads).
Partial htop dump:
2249 www-data 20 0 159M 65544 4676 S 26.0 0.8 2:09.93 mod-wsgi
-k start
2248 www-data 20 0 164M 69040 5560 S 148. 0.8 2:10.72 mod-wsgi
-k start
2274 www-data 20 0 159M 65544 4676 S 0.0 0.8 0:12.58 mod-wsgi
-k start
2250 www-data 20 0 157M 62212 5168 S 10.0 0.7 1:50.35 mod-wsgi
-k start
2291 www-data 20 0 164M 69040 5560 S 41.0 0.8 0:17.07 mod-wsgi
-k start
2251 www-data 20 0 165M 69320 4676 S 0.0 0.8 1:59.48 mod-wsgi
-k start
2272 www-data 20 0 159M 65544 4676 S 0.0 0.8 0:28.67 mod-wsgi
-k start
2282 www-data 20 0 165M 69320 4676 S 0.0 0.8 0:33.85 mod-wsgi
-k start
2292 www-data 20 0 164M 69040 5560 S 28.0 0.8 0:28.08 mod-wsgi
-k start
2298 www-data 20 0 157M 62212 5168 S 0.0 0.7 0:14.93 mod-wsgi
-k start
2299 www-data 20 0 157M 62212 5168 S 1.0 0.7 0:23.71 mod-wsgi
-k start
2358 www-data 20 0 164M 69040 5560 S 1.0 0.8 0:02.62 mod-wsgi
-k start
2252 www-data 20 0 165M 70468 4660 S 41.0 0.8 1:55.85 mod-wsgi
-k start
2273 www-data 20 0 159M 65544 4676 S 10.0 0.8 0:29.03 mod-wsgi
-k start
2278 www-data 20 0 159M 65544 4676 S 1.0 0.8 0:02.79 mod-wsgi
-k start
2264 www-data 20 0 165M 70468 4660 S 0.0 0.8 0:07.50 mod-wsgi
-k start
2266 www-data 20 0 165M 70468 4660 S 25.0 0.8 0:39.49 mod-wsgi
-k start
2300 www-data 20 0 157M 62212 5168 S 6.0 0.7 0:28.78 mod-wsgi
-k start
2265 www-data 20 0 165M 70468 4660 S 15.0 0.8 0:31.44 mod-wsgi
-k start
2294 www-data 20 0 164M 69040 5560 R 54.0 0.8 0:34.82 mod-wsgi
-k start
2279 www-data 20 0 165M 69320 4676 S 0.0 0.8 0:32.63 mod-wsgi
-k start
2297 www-data 20 0 157M 62212 5168 S 3.0 0.7 0:09.68 mod-wsgi
-k start
2302 www-data 20 0 157M 62212 5168 S 0.0 0.7 0:27.62 mod-wsgi
-k
[modwsgi] Re: mod_wsgi Showing more threads in htop than assigned
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:
http://serverfault.com/questions/576527/apache-processes-in-top-more-than-maxclients
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 settings, but am still
experiencing memory creep. Here's my site conf and my apache2.conf:
WSGIDaemonProcess mywsgi user=www-data group=www-data processes=5
threads=5 display-name=mod-wsgi
python-path=/home/admin/.virtualenvs/django/lib/python2.7/site-packages
WSGIPythonHome /home/admin/.virtualenvs/django
WSGIRestrictEmbedded On
WSGILazyInitialization On
VirtualHost 127.0.0.1:8080
ServerName www.mysite.com
DocumentRoot /srv/mysite
SetEnvIf X-Forwarded-Protocol https HTTPS=1
WSGIScriptAlias / /srv/mysite/system/apache/django.wsgi
process-group= mywsgi application-group=%{GLOBAL}
RequestHeader add X-Queue-Start %t
/VirtualHost
IfModule mpm_worker_module
StartServers 1
ThreadsPerChild 5
MinSpareThreads 5
MaxSpareThreads 10
MaxClients 25
ServerLimit 5
MaxRequestsPerChild 0
MaxMemFree1024
/IfModule
I'm watching apache and mod_wsgi via htop and apache seems to be playing
by the rules, never loading more than 25 threads. It usually stays around
10-15 threads. We average around 5-6 requests/second monitored by
/server-status/. The thing that's bothering me is that I'm counting 44
mod_wsgi threads in htop. I assumed that since I had processes=5 threads=5
I would only see a maximum of 30 threads below (5 processes + 25 threads).
Partial htop dump:
2249 www-data 20 0 159M 65544 4676 S 26.0 0.8 2:09.93 mod-wsgi
-k start
2248 www-data 20 0 164M 69040 5560 S 148. 0.8 2:10.72 mod-wsgi
-k start
2274 www-data 20 0 159M 65544 4676 S 0.0 0.8 0:12.58 mod-wsgi
-k start
2250 www-data 20 0 157M 62212 5168 S 10.0 0.7 1:50.35 mod-wsgi
-k start
2291 www-data 20 0 164M 69040 5560 S 41.0 0.8 0:17.07 mod-wsgi
-k start
2251 www-data 20 0 165M 69320 4676 S 0.0 0.8 1:59.48 mod-wsgi
-k start
2272 www-data 20 0 159M 65544 4676 S 0.0 0.8 0:28.67 mod-wsgi
-k start
2282 www-data 20 0 165M 69320 4676 S 0.0 0.8 0:33.85 mod-wsgi
-k start
2292 www-data 20 0 164M 69040 5560 S 28.0 0.8 0:28.08 mod-wsgi
-k start
2298 www-data 20 0 157M 62212 5168 S 0.0 0.7 0:14.93 mod-wsgi
-k start
2299 www-data 20 0 157M 62212 5168 S 1.0 0.7 0:23.71 mod-wsgi
-k start
2358 www-data 20 0 164M 69040 5560 S 1.0 0.8 0:02.62 mod-wsgi
-k start
2252 www-data 20 0 165M 70468 4660 S 41.0 0.8 1:55.85 mod-wsgi
-k start
2273 www-data 20 0 159M 65544 4676 S 10.0 0.8 0:29.03 mod-wsgi
-k start
2278 www-data 20 0 159M 65544 4676 S 1.0 0.8 0:02.79 mod-wsgi
-k start
2264 www-data 20 0 165M 70468 4660 S 0.0 0.8 0:07.50 mod-wsgi
-k start
2266 www-data 20 0 165M 70468 4660 S 25.0 0.8 0:39.49 mod-wsgi
-k start
2300 www-data 20 0 157M 62212 5168 S 6.0 0.7 0:28.78 mod-wsgi
-k start
2265 www-data 20 0 165M 70468 4660 S 15.0 0.8 0:31.44 mod-wsgi
-k start
2294 www-data 20 0 164M 69040 5560 R 54.0 0.8 0:34.82 mod-wsgi
-k start
2279 www-data 20 0 165M 69320 4676 S 0.0 0.8 0:32.63 mod-wsgi
-k start
2297 www-data 20 0 157M 62212 5168 S 3.0 0.7 0:09.68 mod-wsgi
-k start
2302 www-data 20 0 157M 62212 5168 S 0.0 0.7 0:27.62 mod-wsgi
-k start
2323 www-data 20 0 157M 62212 5168 S 0.0 0.7 0:02.56 mod-wsgi
-k start
2280 www-data 20 0 165M 69320 4676 S 0.0 0.8 0:13.00 mod-wsgi
-k start
2263 www-data 20 0 165M 70468 4660 S 0.0 0.8 0:19.35 mod-wsgi
-k start
2322 www-data 20 0 165M 69320 4676 S 0.0 0.8 0:03.05 mod-wsgi
-k start
2275 www-data 20 0 165M 70468 4660 S 0.0 0.8 0:02.72 mod-wsgi
-k start
2285 www-data 20 0 164M 69040 5560 S 0.0 0.8 0:00.00 mod-wsgi
-k start
2288 www-data 20 0 164M 69040 5560 S 0.0 0.8 0:00.11 mod-wsgi
-k start
2290 www-data 20 0 164M 69040 5560 S 4.0 0.8 0:15.66 mod-wsgi
-k start
2293 www-data 20 0 164M 69040 5560 S 20.0 0.8 0:29.01 mod-wsgi
-k start
2268
[modwsgi] Re: mod_wsgi Showing more threads in htop than assigned
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 settings, but am still
experiencing memory creep. Here's my site conf and my apache2.conf:
WSGIDaemonProcess mywsgi user=www-data group=www-data processes=5
threads=5 display-name=mod-wsgi
python-path=/home/admin/.virtualenvs/django/lib/python2.7/site-packages
WSGIPythonHome /home/admin/.virtualenvs/django
WSGIRestrictEmbedded On
WSGILazyInitialization On
VirtualHost 127.0.0.1:8080
ServerName www.mysite.com
DocumentRoot /srv/mysite
SetEnvIf X-Forwarded-Protocol https HTTPS=1
WSGIScriptAlias / /srv/mysite/system/apache/django.wsgi
process-group= mywsgi application-group=%{GLOBAL}
RequestHeader add X-Queue-Start %t
/VirtualHost
IfModule mpm_worker_module
StartServers 1
ThreadsPerChild 5
MinSpareThreads 5
MaxSpareThreads 10
MaxClients 25
ServerLimit 5
MaxRequestsPerChild 0
MaxMemFree1024
/IfModule
I'm watching apache and mod_wsgi via htop and apache seems to be playing
by the rules, never loading more than 25 threads. It usually stays around
10-15 threads. We average around 5-6 requests/second monitored by
/server-status/. The thing that's bothering me is that I'm counting 44
mod_wsgi threads in htop. I assumed that since I had processes=5 threads=5
I would only see a maximum of 30 threads below (5 processes + 25 threads).
Partial htop dump:
2249 www-data 20 0 159M 65544 4676 S 26.0 0.8 2:09.93 mod-wsgi
-k start
2248 www-data 20 0 164M 69040 5560 S 148. 0.8 2:10.72 mod-wsgi
-k start
2274 www-data 20 0 159M 65544 4676 S 0.0 0.8 0:12.58 mod-wsgi
-k start
2250 www-data 20 0 157M 62212 5168 S 10.0 0.7 1:50.35 mod-wsgi
-k start
2291 www-data 20 0 164M 69040 5560 S 41.0 0.8 0:17.07 mod-wsgi
-k start
2251 www-data 20 0 165M 69320 4676 S 0.0 0.8 1:59.48 mod-wsgi
-k start
2272 www-data 20 0 159M 65544 4676 S 0.0 0.8 0:28.67 mod-wsgi
-k start
2282 www-data 20 0 165M 69320 4676 S 0.0 0.8 0:33.85 mod-wsgi
-k start
2292 www-data 20 0 164M 69040 5560 S 28.0 0.8 0:28.08 mod-wsgi
-k start
2298 www-data 20 0 157M 62212 5168 S 0.0 0.7 0:14.93 mod-wsgi
-k start
2299 www-data 20 0 157M 62212 5168 S 1.0 0.7 0:23.71 mod-wsgi
-k start
2358 www-data 20 0 164M 69040 5560 S 1.0 0.8 0:02.62 mod-wsgi
-k start
2252 www-data 20 0 165M 70468 4660 S 41.0 0.8 1:55.85 mod-wsgi
-k start
2273 www-data 20 0 159M 65544 4676 S 10.0 0.8 0:29.03 mod-wsgi
-k start
2278 www-data 20 0 159M 65544 4676 S 1.0 0.8 0:02.79 mod-wsgi
-k start
2264 www-data 20 0 165M 70468 4660 S 0.0 0.8 0:07.50 mod-wsgi
-k start
2266 www-data 20 0 165M 70468 4660 S 25.0 0.8 0:39.49 mod-wsgi
-k start
2300 www-data 20 0 157M 62212 5168 S 6.0 0.7 0:28.78 mod-wsgi
-k start
2265 www-data 20 0 165M 70468 4660 S 15.0 0.8 0:31.44 mod-wsgi
-k start
2294 www-data 20 0 164M 69040 5560 R 54.0 0.8 0:34.82 mod-wsgi
-k start
2279 www-data 20 0 165M 69320 4676 S 0.0 0.8 0:32.63 mod-wsgi
-k start
2297 www-data 20 0 157M 62212 5168 S 3.0 0.7 0:09.68 mod-wsgi
-k start
2302 www-data 20 0 157M 62212 5168 S 0.0 0.7 0:27.62 mod-wsgi
-k start
2323 www-data 20 0 157M 62212 5168 S 0.0 0.7 0:02.56 mod-wsgi
-k start
2280 www-data 20 0 165M 69320 4676 S 0.0 0.8 0:13.00 mod-wsgi
-k start
2263 www-data 20 0 165M 70468 4660 S 0.0 0.8 0:19.35 mod-wsgi
-k start
2322 www-data 20 0 165M 69320 4676 S 0.0 0.8 0:03.05 mod-wsgi
-k start
2275 www-data 20 0 165M 70468 4660 S 0.0 0.8 0:02.72 mod-wsgi
-k start
2285 www-data 20 0 164M 69040 5560 S 0.0 0.8 0:00.00 mod-wsgi
-k start
2288 www-data 20 0 164M 69040 5560 S 0.0 0.8 0:00.11 mod-wsgi
-k start
2290 www-data 20 0 164M 69040 5560 S 4.0 0.8 0:15.66 mod-wsgi
-k start
2293 www-data 20 0 164M 69040 5560 S 20.0 0.8 0:29.01 mod-wsgi
-k start
2268 www-data 20 0 159M 65544 4676 S 0.0 0.8 0:00.00 mod-wsgi
-k start
2269 www-data 20 0 159M 65544 4676 S 0.0 0.8 0:00.11 mod-wsgi
-k start
2270 www-data 20 0 159M 65544 4676 S 15.0 0.8 0:26.62 mod-wsgi
-k start
