Incrasing the amount of Python workers

Repository of web frameworks and applications for Microsoft IIS.
User avatar
Posts: 56
Joined: 01 Nov 2013, 01:50

Incrasing the amount of Python workers

26 May 2014, 09:24

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)?

User avatar
Posts: 871
Joined: 12 Mar 2012, 09:54

Re: Incrasing the amount of Python workers

26 May 2014, 09:45

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.

User avatar
Posts: 56
Joined: 01 Nov 2013, 01:50

Re: Incrasing the amount of Python workers

26 May 2014, 11:10

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>

User avatar
Posts: 871
Joined: 12 Mar 2012, 09:54

Re: Incrasing the amount of Python workers

27 May 2014, 06:13

Hello,

You can't specify that in web.config for security reasons. You can only set <userEngines> in applicationHost.config.

User avatar
Posts: 56
Joined: 01 Nov 2013, 01:50

Re: Incrasing the amount of Python workers

27 May 2014, 09:40

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.

User avatar
Posts: 871
Joined: 12 Mar 2012, 09:54

Re: Incrasing the amount of Python workers

28 May 2014, 09:39

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.

Return to Helicon Zoo

Who is online

Users browsing this forum: No registered users and 15 guests