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
> MaxMemFree 1024
> </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
> 2271 www-data 20 0 159M 65544 4676 S 0.0 0.8 0:26.55 mod-wsgi
> -k start
>
> Last night I had processes=3 threads=3 and my NR capacity report reported
> 100% usage (
> https://rpm.newrelic.com/accounts/67402/applications/1132078/optimize/capacity_analysis),
>
> so I upped it to processes=5 threads=5 and now I have 44 threads going.
> Despite the instance count reported by NR staying relatively stable, memory
> consumption continues to increase (
> https://rpm.newrelic.com/accounts/67402/servers/1130000/processes#id=152494639).
>
> I realize that nobody except for Graham can see those NR reports, sorry.
>
> Has anyone dealt with this situation before?
>
> Mark
>
>
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/groups/opt_out.
