Incrasing the amount of Python workers
6 posts
• Page 1 of 1
Incrasing the amount of Python workers
Our application is DB I/O bound, hence running a single Python worker process per CPU is not enough for our performance needs.
How it possible to increase the amount of worker processes per CPU (similar to mod_wsgi for example)?
How it possible to increase the amount of worker processes per CPU (similar to mod_wsgi for example)?
Re: Incrasing the amount of Python workers
Hello,
Please set maxInstances="10" minInstances="10" in engine settings in Zoo to as many as you consider necessary.
It's better to have min=maх then module won't need to create/delete them.
Please set maxInstances="10" minInstances="10" in engine settings in Zoo to as many as you consider necessary.
It's better to have min=maх then module won't need to create/delete them.
Re: Incrasing the amount of Python workers
Thanks for the fast reply!
Can we set them right inside the web.config, say:
<userEngines>
<add name="python 2.7" displayName="Python 2.7" protocol="fastcgi" minInstances="15" maxInstances="15"/>
</userEngines>
Can we set them right inside the web.config, say:
<userEngines>
<add name="python 2.7" displayName="Python 2.7" protocol="fastcgi" minInstances="15" maxInstances="15"/>
</userEngines>
Re: Incrasing the amount of Python workers
Hello,
You can't specify that in web.config for security reasons. You can only set <userEngines> in applicationHost.config.
You can't specify that in web.config for security reasons. You can only set <userEngines> in applicationHost.config.
Re: Incrasing the amount of Python workers
I see, thanks for the advice.
One last question, I was sure that all Helicon DJango apps by default are FastCGI, but I see in app settings (in Zoo manager) the default engine being WSGI, is this correct?
Also, is this a real WSGI supporting all performance and security enhancements (as the mod_wsgi in Apache)?
Thanks.
One last question, I was sure that all Helicon DJango apps by default are FastCGI, but I see in app settings (in Zoo manager) the default engine being WSGI, is this correct?
Also, is this a real WSGI supporting all performance and security enhancements (as the mod_wsgi in Apache)?
Thanks.
Re: Incrasing the amount of Python workers
Hello,
FastCGI and WSGI in Zoo are now the same. We have just renamed from FastCGI into WSGI.
Our solution is rather different from mod_wsgi - we have Python processes running outside w3wp and communication between them is done via FastCGI. Python workers are not visible to anyone from outside the server. Security is provided by IIS, Windows, firewalls. We do not do anything specific to ensure security.
FastCGI and WSGI in Zoo are now the same. We have just renamed from FastCGI into WSGI.
Our solution is rather different from mod_wsgi - we have Python processes running outside w3wp and communication between them is done via FastCGI. Python workers are not visible to anyone from outside the server. Security is provided by IIS, Windows, firewalls. We do not do anything specific to ensure security.
6 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 0 guests