Oh thanks a lot! I will add --close-on-exec then. i also trying --cpu-affinity
On Thu, Mar 8, 2012 at 9:31 PM, Roberto De Ioris <[email protected]> wrote: > > > Hello > > > > I am testing web2py with uWSGI and some request have random timeout > (after > > IO Heavy operation is started , but it is spawned using > > subprocess.Popen()) > > And then progress is selected from DB Every 5 Seconds (Progress Percent > > Insert,Commit to db is only done at each 5% intervals) > > At the IO Heavy times , the progress status is Timedout! even tho I set > > timeouts to really huge 6000 secs , it still timeout. > > If you generate a process during a request it will inherit the opened file > descriptors. Add --close-on-exec to uWSGI to let it automatically close > opened sockets before execing a new process. > > > > > Also it seems that all uWSGI worker processes are running at the same > core > > as extraction process is running . how can i make it run in different > > cores > > (to make use of multple cores?) > > > > > > I think you are referring to 'uwsgi cores' in the logs. They are referred > to threads and async modes. They do not reflect the cpu core in which it > is running. > > > -- > Roberto De Ioris > http://unbit.it >
