|
#2
| |||
| |||
|
Il giorno mer, 19/05/2010 alle 14.55 -0700, Dan McComas ha scritto:
> I am trying to get a deployment on ec2 running currently on ubuntu > 9.10 and am running into a ton of errors while load testing. I am > totally unsure of whether there is a bug somewhere or if our > configuration is not great. > Hi Dan, you are stressing your system with a too high load for your setup. In your setup nginx is trying to connect to the uWSGI server, but (as it is working on previous request) it will not answer to nginx. Then nginx will timeout. If you stop your test, you will seee nginx and uWSGI start working again. If you really want to increase tolerance of nginx you have to increse the upstream connect timeout using the option uwsgi_connect_timeout Set it (for example) at 30 seconds You can even increase the backlog queue of the uWSGI socket (but this is not a good choice) using the -l flag. You can even try adding more processes in uWSGI (but remember to use -M) -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi ) |
|
#3
| |||
| |||
|
uwsgi
) |
|
#4
| |||
| |||
|
Il giorno gio, 20/05/2010 alle 08.25 -0700, Dan McComas ha scritto:
> Could you reccomend a number of processes per core? It is application dependent, but as django is often in waiting-state (waiting for query result), i think that a couple of processes per core should be enough |