tag:blogger.com,1999:blog-2363643920942057324.post3167667529418787563..comments2023-08-09T23:00:54.857+10:00Comments on Graham Dumpleton: Save on memory with mod_wsgi 3.0.Graham Dumpletonhttp://www.blogger.com/profile/13609779138164842374noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-2363643920942057324.post-35092555518745806932010-10-23T07:52:14.692+11:002010-10-23T07:52:14.692+11:00Yes, WSGILazyInitialization must be at server conf...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#WSGILazyInitializationGraham Dumpletonhttps://www.blogger.com/profile/13609779138164842374noreply@blogger.comtag:blogger.com,1999:blog-2363643920942057324.post-40290470597696301842010-10-22T23:12:41.261+11:002010-10-22T23:12:41.261+11:00I'm gradually working through the pages releva...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.<br /><br />So, just to be crystal clear: the presumption is that <b>WSGILazyInitialization</b> must also be set at global scope, as is the case with <b>WSGIRestrictEmbedded</b>?Dave Everitthttps://www.blogger.com/profile/07555844691507763899noreply@blogger.comtag:blogger.com,1999:blog-2363643920942057324.post-42353976151260429382009-11-26T22:33:07.170+11:002009-11-26T22:33:07.170+11:00Hmmm, I kept saying mod_wsgi 3.0. Actually, mod_ws...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.Graham Dumpletonhttps://www.blogger.com/profile/13609779138164842374noreply@blogger.com