On Sunday, November 30, 2014 1:51:37 PM UTC+1, nick name wrote: > > Is that true even with immediate=True? If so, what is the recommended way > to reduce this to 0.5 seconds or so? I have an app in which a user requests > somethng; that request launches 1-10 other web requests, and the user keeps > refreshing until they all complete for the summarized result. (I will > probably replace this with an ajax poll or a ws notification instead later > on). > >> >>>>> mine was just a general checklist before anything else, since several minutes point towards another whole set of issues. in general, immediate=True shortcircuits the 5 loops wait in assigning newly created tasks. so, in worst case scenario, you'll have
|---sched.queue_task(....)---|---sleep---|---sleep---|---sleep---|---sleep---|---ASSIGNING---|---RUNNING---| (without immediate) |---sched.queue_task(....,immediate=True)---|---ASSIGNING---|---RUNNING---| (with immediate) every |---something---| is by default a loop that last 3 seconds (the heartbeat value on initialization) Simone -- 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.
