Skip to content
Discussion options

You must be logged in to vote

run_periodic_tasks() is not driven by a separate fixed timer. It is called by the backend worker when the worker reaches its idle/maintenance part of the poll loop: after it has attempted to read frontend queues and there are no cached transit events to process.

With the default backend options, once the backend is idle it then sleeps for BackendOptions::sleep_duration, which defaults to 100us, so in an idle application run_periodic_tasks() can be called roughly once per backend wake cycle. This is not a hard real-time interval: OS scheduling, backend work, sink work, and configured options affect it. If sleep_duration is set to 0, it may be called very frequently; if sleep_duration is lo…

Replies: 5 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Answer selected by fahrudinhalilovic
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@fahrudinhalilovic
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants