<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr"><br></div><div dir="ltr"><br><blockquote type="cite">On 19 Aug 2024, at 06:55, Windl, Ulrich <u.windl@ukr.de> wrote:<br><br></blockquote><br></div><blockquote type="cite"><div dir="ltr"><span>Despite of the fact that my version of systemd does not know that setting, can you explain what the effect of AccuracySec= really is?</span><br><span></span></div></blockquote><div><br></div><div>The docs <a href="https://www.man7.org/linux/man-pages/man5/systemd.timer.5.html">https://www.man7.org/linux/man-pages/man5/systemd.timer.5.html</a> say this</div><div><br></div><div><pre style="font-size: 16px; -webkit-text-size-adjust: auto; margin-left: 8px; font-family: monospace, courier; caret-color: rgb(28, 28, 28); color: rgb(28, 28, 28); background-color: rgb(255, 255, 255);"> Note that this setting is primarily a power saving option
that allows coalescing CPU wake-ups. It should not be
confused with <i style="color: rgb(54, 54, 54);">RandomizedDelaySec=</i> (see below) which adds a
random value to the time the timer shall elapse next and
whose purpose is the opposite: to stretch elapsing of timer
events over a longer period to reduce workload spikes. For
further details and explanations and how both settings play
together, see below.</pre></div><div>So if you have 5 timers that expire about the same time this allows them to all run at the sane time thus saving power.</div><div><br></div><div>Barry</div><div><br></div><div><br></div></body></html>