Comments on Graham Dumpleton: Save on memory with mod_wsgi 3.0.

Yes, WSGILazyInitialization must be at server conf...

2010-10-23T07:52:14.692+11:00

Yes, WSGILazyInitialization must be at server config level. See http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives#WSGIRestrictEmbedded and http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives#WSGILazyInitialization

I'm gradually working through the pages releva...

2010-10-22T23:12:41.261+11:00

I'm gradually working through the pages relevant to running Django and, for my own reference, condensing your extremely informative info to the absolutely necessary as I proceed.

So, just to be crystal clear: the presumption is that WSGILazyInitialization must also be set at global scope, as is the case with WSGIRestrictEmbedded?

Hmmm, I kept saying mod_wsgi 3.0. Actually, mod_ws...

2009-11-26T22:33:07.170+11:00

Hmmm, I kept saying mod_wsgi 3.0. Actually, mod_wsgi 3.1 is already available, although it was only a slight change to address a build issue. So, if already have mod_wsgi 3.0 and it is working, no need to upgrade to 3.1 at this point.