I\'ve seen two strategies for hosting a django application with gunicorn and nginx.
One strategy is to run gunicorn on a network port. For example (from http://goodcode
Here are the results of my test TCP Proxy via Unix socket:
Setup: nginx + gunicorn + django running on 4 m4.xlarge nodes on AWS.
1 million of requests are made over about 30 minute window:
one instance is at 100% and 3 others are all 70% CPU because of app internal load distribution.
TCP vs. socket is virtually identical
Timing for making 1000000 requests
is 27 minutes for TCP proxy
and 31 minutes for the unix socket.
In this particular setup no unix socket performance advantage.