if threads=0 does not work use threads=1 and make mod_wsgi happy. If you remove threads it defaults to 15.
2014-03-19 4:34 GMT+01:00 horridohobbyist <horrido.hobb...@gmail.com>: > "threads=0" is no good–Apache restart upchucks on this. > > BTW, I haven't experimented with the threads value. Might this also improve > performance (with respect to GIL)? > > Also, I was wondering. Is the "processes=" solution related to whether you > are using the "prefork" MPM or the "worker" MPM? I know that Apache is > normally compiled to use the prefork MPM. > > > On Tuesday, 18 March 2014 16:26:24 UTC-4, Michele Comitini wrote: >> >> > WSGIDaemonProcess hello user=www-data group=www-data threads=5 >> >> with web2py try the following instead: >> WSGIDaemonProcess hello user=www-data group=www-data processes=<number >> of cores + 1> threads=(0 or 1) >> >> If it's faster, then the GIL must be the cause. flask by default has >> much less features active (session for instance) >> >> >> >> 2014-03-18 21:04 GMT+01:00 horridohobbyist <horrido...@gmail.com>: >> > I took the shipping code that I ran in Flask (without Apache) and >> > adapted it >> > to run under Apache as a Flask app. That way, I'm comparing apples to >> > apples. I'm comparing the performance of the shipping code between Flask >> > and >> > web2py. >> > >> > Below, I've included the 'default' file from Apache2/sites-available for >> > Flask. >> > >> > Basically, the code in Flask executes 10x faster than the same code in >> > web2py. So my question is: if Apache is at fault for the web2py app's >> > slow >> > performance, why doesn't Apache hurt the Flask app's performance? (This >> > doesn't seem to be related to GIL or WSGI.) >> > >> > >> > <VirtualHost *:80> >> > ServerName 10.211.55.7 >> > WSGIDaemonProcess hello user=www-data group=www-data threads=5 >> > WSGIScriptAlias / /home/richard/welcome/hello.wsgi >> > >> > <Directory /home/richard/welcome> >> > Order Allow,Deny >> > Allow from all >> > </Directory> >> > </VirtualHost> >> > >> > -- >> > Resources: >> > - http://web2py.com >> > - http://web2py.com/book (Documentation) >> > - http://github.com/web2py/web2py (Source code) >> > - https://code.google.com/p/web2py/issues/list (Report Issues) >> > --- >> > You received this message because you are subscribed to the Google >> > Groups >> > "web2py-users" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> > an >> > email to web2py+un...@googlegroups.com. >> > For more options, visit https://groups.google.com/d/optout. > > -- > Resources: > - http://web2py.com > - http://web2py.com/book (Documentation) > - http://github.com/web2py/web2py (Source code) > - https://code.google.com/p/web2py/issues/list (Report Issues) > --- > You received this message because you are subscribed to the Google Groups > "web2py-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to web2py+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
