Il giorno 02/mag/2012, alle ore 08:55, Ryan Showalter ha scritto: > Hello, > > I've noticed that with recent version of uWSGI, the spooler does not > treat jobs as it used to. Before, if 10 jobs were in the queue and job > 1 failed, the spooler would proceed to try job 2 and then job 3, etc. > But recently, I've noticed that if job1 fails, it will continue to try > and execute job1 completely ignoring jobs 2-10 until job1 is > successfully processed. Here is my config:
This is pretty strange, as the spooler is not supposed to work in that way. How the job is failing ? I mean, it is returning a SPOOL_RETRY or an Exception ? > > > Also, on a slightly related note.. I've noticed that the spooler > workers will occasionally take up VAST amounts of memory (upwards of > 256MB) with no jobs in the queue. This is why I've set the > spooler-max-tasks option, but it's even happened to me once with that > option set. I don't currently have debug logs from when this has > happened but I'll post them when it happens to me again. > The spooler can only destroy objects created by him, if the code you are running cannot be freed it will leak. I suggest you to use sys.gettotalrefcount() before exiting the function to see if your callable is leaking -- Roberto De Ioris http://unbit.it JID: [email protected] _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
