On Monday, June 6, 2016 at 5:30:50 PM UTC-4, Niphlod wrote: > > okay but ..... > """ > Withimmediate=True you can force the check for new tasks: it will happen > at most as heartbeat seconds are passed > """ > clearly states that "it" is "check for new tasks". >
Yes, but earlier it says: immediate=True it will force the main worker to reassign tasks. So, you would assume that a "check for new tasks" results in the immediate assignment of such tasks. However, it sounds like even after a check for new tasks, there can still be a lag of several heartbeats before new tasks are actually assigned. In the task lifecycle diagram, it might be helpful to show what kinds of lags to expect at each of the arrows (and what causes the lag, such as waiting for a set number of heartbeats or simply waiting for a worker to complete previously assigned tasks before it can get to the next one). 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
