2009/12/2 peter2108 <[email protected]>:
> I compiled Apache with 'worker' MPM and installed v3.1 of mod-wsgi
> using the webfaction forum post you pointed out to me. I used the
> Apache conf as in the post but added WSGIRestrictEmbedded On. This
> seems to work fine. The RSS values (obtained using 'ps' )
> are:
>
> Original 'prefork'
>  RSS    SZ   PID
>  1948   936  6774 /home/username/webapps/bimmdjango/apache2/bin/httpd
>  3336  1932  6781 /home/username/webapps/bimmdjango/apache2/bin/httpd
>  3336  1932  6782 /home/username/webapps/bimmdjango/apache2/bin/httpd
>
> New 'worker'
>  2144  1072  27533 /home/username/webapps/bimmdjango/apache2/bin/
> httpd
>  3612 227336 27539 /home/username/webapps/bimmdjango/apache2/bin/
> httpd  (mod_wsgi)
>  1940 226440 27563 /home/username/webapps/bimmdjango/apache2/bin/
> httpd
>
> which is an 11% saving. I don't know how the values on the webfaction
> forum were obtained so I
> can't say if these are as expected.

If you happy to fiddle a bit more. Using mod_wsgi 3.1, you might
compare that to using:

WSGILazyInitialization Off
WSGIRestrictedEmbedded Off

This effectively restores 3.1 behaviour to what it was with 2.X.

That way you can see what 3.1 would have looked like under worker MPM
with old way of doing things.

This will give a better indication of whether the lazy initialisation
and restrictions on embedded mode is working for that MPM.

It is a bit fuzzy at the moment as to what sort of configurations you
might see less memory used with what is now the default in 3.1. So,
some feedback would be nice.

Graham

--

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.


Reply via email to