On Friday, September 18, 2015 at 3:37:26 PM UTC-4, Phillip wrote: > > This was my basic interpretation of your post: Scheduler processes > shouldn't be managed by the webserver (shouldn't be controlled by user > requests) which could basically create zombie processess and / or will drop > long-running processes. >
This just means that the web server (or the app) should not *start the workers*. Instead, when you start the server running, you also start a bunch of background worker processes. Then, as users make requests for the long-running jobs, those jobs are passed off to one of the available workers. The number of workers that can be running depends on the resources of the machine. Even if all the workers are busy at a given moment, though, as soon as one frees up, the next task will be pulled off the queue. So, as long as your app isn't receiving requests at a pace faster than the hardware can do the jobs, all the jobs will eventually complete. Anthony -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
