Proxy or fastcgi for python app

Server NGINX
1

Hi,

I’m going to try nginx with somes python apps. Thanks to wsgi i can
easily choose between fastcgi or proxy.

How can i choose ?

I don’t care if one is a little bit more or less fast. My problem is to
run on a small system (vps) with some non-thread-safe applications (but
fast enough).

Thanks

2

On 01-09-2009, William Dode wrote:

Hi,

I’m going to try nginx with somes python apps. Thanks to wsgi i can
easily choose between fastcgi or proxy.

How can i choose ?

I answer to myself after reading :

http://www.vmunix.com/mark/blog/archives/2006/01/02/fastcgi-scgi-and-apache-background-and-future/

http://blog.ianbicking.org/fastcgi-scgi-http.html

So, please say me if i’m wrong.

I should use fastcgi if i want more control on the environement between
nginx and my app.
I should use httpproxy if i want more autonomy for my app (choose my
http server, - cherrypy paste wsgiref… - for example)

3

On Tue, 2009-09-01 at 11:24 +0000, William Dode wrote:

http://www.vmunix.com/mark/blog/archives/2006/01/02/fastcgi-scgi-and-apache-background-and-future/

http://blog.ianbicking.org/fastcgi-scgi-http.html

So, please say me if i’m wrong.

I should use fastcgi if i want more control on the environement between
nginx and my app.
I should use httpproxy if i want more autonomy for my app (choose my
http server, - cherrypy paste wsgiref… - for example)

It doesn’t really matter. I personally prefer proxying as it is
slightly simpler.

Cliff

4

I’m going to try nginx with somes python apps. Thanks to wsgi i can
easily choose between fastcgi or proxy.

How can i choose ?

Test, test and test some more :wink:

I’m using wsgiserver from CherryPy (so proxied webserver).

Best regards,
Piotr S. < [email protected] >

5

On Sep 1, 2009, at 12:41, “Piotr S.” [email protected]
wrote:

I’m going to try nginx with somes python apps. Thanks to wsgi i can
easily choose between fastcgi or proxy.

How can i choose ?

Test, test and test some more :wink:

I’m using wsgiserver from CherryPy (so proxied webserver).

Recently we moved from using fastcgi, to http proxy for our django app.

On the python side we are using Spawning, which was developed at
Linden Lab I believe.

It’s quite nice, and very light weight / fast. It seems to be thread
safe too.

It starts a process which forks I/o processes the i/o procesed can
either use forking or threading (we use threading). The master process
manages them, restarting them if they die etc. It handles incoming
connections and passes them to a free child process.

Fast, clean, efficient.

6

On Thu, 2009-09-03 at 10:09 +0100, Avleen Vig wrote:

I’m using wsgiserver from CherryPy (so proxied webserver).

Recently we moved from using fastcgi, to http proxy for our django app.

On the python side we are using Spawning, which was developed at
Linden Lab I believe.

I use Spawning as well and can attest that it works quite well.

Cliff

7

Hi,

Just to say that i migrated 30 python web apps (on two vps) from
apache+mod_wsgi to nginx+http-proxy with success.

I did it in two step. First i migrated apache+mod_wsgi to apache+proxy
and after to nginx+proxy. I didn’t think it’ll be so easy. Now it’s fun
to see the graph of process going down !

spacibo Igor

8

On 03-09-2009, Avleen Vig wrote:

I’m using wsgiserver from CherryPy (so proxied webserver).

Recently we moved from using fastcgi, to http proxy for our django app.

On the python side we are using Spawning, which was developed at
Linden Lab I believe.

Thanks, i didn’t know.

I will begin to try http proxy and see…