uhm. maybe it's not strictly clear but what immediate does is checking for new tasks (and the assigning/reassigning cycle) ASAP. There's no guarantee to do anything else (e.g. unavailable workers, single worker occupied processing a previous task, available workers but with a different group_name, etc).
If you pinpoint the piece on the book that says they'll be picked up within hearbeat with immediate=True, we can review it On Friday, June 3, 2016 at 10:18:47 PM UTC+2, Anthony wrote: > > >> > The documentation claims tasks will be picked up within one heartbeat with > immediate=True, though in this case it looks like it's taking at least > three heartbeats. Is that to be expected unless using redis, in which case, > we should update the docs? > > 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.
