On 21. Aug 2024, at 12.35, Timo Sirainen <t...@sirainen.com> wrote: > > The way Dovecot works is: > - It finds the next timeout, sees that it happens in e.g. 5 milliseconds. > - Then it calls kqueue() to wait for I/O for max 5 milliseconds > - Then it notices that it actually returned more than 105 milliseconds later, > and then logs a warning about it. > > So kqueue() apparently isn't very accurate in its timeout handling.
Actually another guess: Some people were saying it happens mainly on idle hours. Maybe kqueue() is accurate with low timeout values, but not accurate on high timeout values? So if Dovecot asked kqueue() to wait for <100ms, it would be very accurate. But if it asks to wait for 10000ms, kqueue() would think it's okay to return after 10100ms. If that's the case, this check could be changed to allow higher time jumps only on higher timeout waits. _______________________________________________ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
