https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6996
--- Comment #6 from Mark Martinec <[email protected]> --- (In reply to Kevin A. McGrail from comment #5) > So to follow up RW's comments, Round-robin is a "not recommended" option > anyway but since the patch is done do we want to consider it a fix > and move on? Mark, I believe you committed it. > Do I need to make an rc6 for testing? I was hoping for some feedback from Jan Hejl who reported the issue originally. But yes, the patch has been committed, I've tested a couple of scenarios (on Unix, not Windows) with multiple clients, with and without --round-robin, observing the debug log. Seems to work as expected - although I'm not using spamd in production (running amavis here), so it can't hurt to do another RC. Not directly relevant to this problem report, but regarding the comment #4: I agree with the explanation there, but need to add a remark. When the number of child processes roughly matches the load so that most of them are busy most of the time, and the number of processes does not exceed the host's memory size, then autonomous/random scheduling is no worse than the 'managed' approach. On the other hand, if the number of child processes is large and a sizable share of them are idle, so they get paged out, then in my opinion the problem is in the configuration which should not allow more processes to exist than a host can handle, and not many more than are actually needed. In the end, it all boils down to how SpamAssassin is integrated with a mailing system (before-queue or after-queue with MTA, or invoked at the time of a mail delivery to a mailbox, or when a mail client accesses its mailbox). -- You are receiving this mail because: You are the assignee for the bug.
