On 2025/12/15 1:01 PM, Rich via Exim-users wrote:
In scrolling through mainlog again, I note that lots of queue runners were ended with "Abandon queue run: (load 12.84, max 12.00)."
While your choice of system load limit is up to you, 12 feels low. It depends on your hardware, details of how your OS counts that, and whether you need to reserve capacity for other work. Back in the day I used to suggest to people that cpu-core-count + disk-spindle-count was a good dividing line between "under-utilised" and "starting to queue" on Linux.
Is it because qq is load-intensive in phase 1?
We don't know yet.
But it still seemed odd that as soon as I switched to -q not -qq deliveries started flowing out and there were no more abandoned queue runner jobs.
-qq has more possibilities for firing off work in parallel, which if you are bumping into the load-limit would then get abandoned (I'll look into a possible tweak on that). You could experiment with the "-oY" cmdline option in combination with "-qq"; it will disable some of those possibilities (at the cost of fast ramp-up of queue runners, so you'd want to keep that 10s period. For the normal case with -qq you don't need such a short period in most cases). -qq or not, for this sort of load I do hope you're running a local caching resolver. Also, depending on how the filesystem implementation behaves with 80k-size directories it might be worth experimenting with split-spool. -- Cheers, Jeremy -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ ## unsubscribe (doesn't require an account): ## [email protected] ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
