> I can recreate the problem by just hitting a page with about 90 requests > in > 5 seconds. So I guess about 20 requests per second. > > It looks like it is only happening with uWsgi requests. Static pages seem > to work great. > > My current command line options for uWsgi are: > /usr/bin/uwsgi -s 127.0.0.1:45516 -t 60 -M -p 10 -C -x > /......../uwsgi.xml > > I've tried playing with -t and -p but doesn't seem to change the outcome. > I > guess I'll check over at uWsgi for more trouble shooting.
I Paul, you have to check the uWSGI server log. If it is a configuration problem it will log it. Remember that uWSGI is very conservative by default. It will not spawn other workers if the load increment but the hardware resources are not enough so if your 10 processes is not enough you have to increase them. - But increasing processes rarely is a solution - I bet that your problem is on the socket-side. Look at the -z (internal timeout) and -l (socket backlog) options. Put them at large value like -z 30 -l 128 and the cherokee timeout should go away. They are value that are "application" dependent so do not try to find a "work-for-all" value. -- Roberto De Ioris http://unbit.it -- _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
