LoopingCall sleep interval does not account for duration of last tasks run
Bug #1079725 reported by
Eoghan Glynn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslo-incubator |
Fix Released
|
Medium
|
Eoghan Glynn | ||
Grizzly |
Fix Released
|
Medium
|
Eoghan Glynn |
Bug Description
The time spent executing tasks is not accounted for when determining how much time to sleep between task runs.
So for example if periodic_interval is set to N seconds, the actual time between tasks is of the order of:
N + \Sigma duration(task_i)/(1 + ticks for task_i)
The more tasks with ticks=0, and the longer the task duration, the more we skew away from tasks executing on wall-clock boundaries.
As discussed on:
http://
Changed in oslo: | |
assignee: | nobody → Eoghan Glynn (eglynn) |
status: | New → In Progress |
Changed in oslo: | |
importance: | Undecided → Medium |
Changed in oslo: | |
status: | In Progress → Fix Committed |
Changed in oslo: | |
milestone: | none → grizzly-2 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.