mirror of
https://github.com/mailscope/kumomta.git
synced 2026-10-23 06:52:26 +00:00
Wez Furlong
10193434a8
To facilitate this, some adjustments needed to be made to the time calculation in the maintainer because we previously didn't consider it to be valid to have a retry_interval below 1 minute, but in order for this integration test to be viable to run as part of the CI it needs to run in significantly less time than 1 minute. The approach taken here is to avoid considering 1 minute as the baseline, but rather take 1/20th of the retry_interval. In the default configuration, the numbers work out the same as previously, but they will scale down as the retry_interval is reduced. Care is taken to avoid a couple of borderline busy wait scenarios where we might otherwise have woken up at unrealistically small intervals: timeq can suggest 1ms in a few scenarios, and we just round those up to the next second to avoid that. It's worth noting that we do not consider the scheduled queue to be a realtime, high granularity queue: anything that lands there is considered to be bulk/batch and will be handled later: it isn't worth prioritizing with high granularity because messages that land there are generally not going to be delivered quickly.