|
260 | 260 |
|
261 | 261 | <listitem><para>Delay the timer by a randomly selected, evenly distributed amount of time between 0
|
262 | 262 | and the specified time value. Defaults to 0, indicating that no randomized delay shall be applied.
|
263 |
| - Each timer unit will determine this delay randomly before each iteration, and the delay will simply |
264 |
| - be added on top of the next determined elapsing time, unless modified with |
265 |
| - <varname>FixedRandomDelay=</varname>, see below.</para> |
| 263 | + Each timer unit will determine this delay randomly before each iteration, unless modified with |
| 264 | + <varname>FixedRandomDelay=</varname>, see below. The delay is added on top of the next determined |
| 265 | + elapsing time or the service manager's startup time, whichever is later.</para> |
266 | 266 |
|
267 | 267 | <para>This setting is useful to stretch dispatching of similarly configured timer events over a
|
268 | 268 | certain time interval, to prevent them from firing all at the same time, possibly resulting in
|
|
284 | 284 | <varlistentry>
|
285 | 285 | <term><varname>FixedRandomDelay=</varname></term>
|
286 | 286 |
|
287 |
| - <listitem><para>Takes a boolean argument. When enabled, the randomized offset specified by |
288 |
| - <varname>RandomizedDelaySec=</varname> is reused for all firings of the same timer. For a given timer |
289 |
| - unit, the offset depends on the machine ID, user identifier and timer name, which means that it is |
290 |
| - stable between restarts of the manager. This effectively creates a fixed offset for an individual |
291 |
| - timer, reducing the jitter in firings of this timer, while still avoiding firing at the same time as |
292 |
| - other similarly configured timers.</para> |
| 287 | + <listitem><para>Takes a boolean argument. When enabled, the randomized delay specified by |
| 288 | + <varname>RandomizedDelaySec=</varname> is chosen deterministically, and remains stable between all |
| 289 | + firings of the same timer, even if the manager is restarted. The delay is derived from the machine |
| 290 | + ID, the manager's user identifier, and the timer unit's name. This effectively creates a unique fixed |
| 291 | + offset for each timer, reducing the jitter in firings of an individual timer while still avoiding |
| 292 | + firing at the same time as other similarly configured timers.</para> |
293 | 293 |
|
294 | 294 | <para>This setting has no effect if <varname>RandomizedDelaySec=</varname> is set to 0. Defaults to
|
295 | 295 | <option>false</option>.</para></listitem>
|
|
0 commit comments