https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6075
--- Comment #28 from Mark Martinec <[email protected]> 2009-03-03 16:43:36 PST --- > No problem, and in fact thanks for sticking with it this long. i'm very happy > to have documented in the record these difficult to debug problems that could > arise from a high speed connection throttled by a lower speed upstream, or by > high rate UDP getting throttled by a Zyxel or similarly performing router. I wonder how common this problem is. Thanks to Elsa for perseverance! How many SOHO users of SpamAssassin suffer from this without knowing? It might be possible to implement application-level traffic shaping (leaky bucket or token bucket algorithm) for taming UDP storms. The main problem seems to be lack of fine granularity in tasks of SA (and the absence of fine granularity interrupts in Perl). Something like a 10 ms scheduling event would do for the purpose, and could also help with more prompt harvesting of responses (Bug 5589 comment 7). A Bug 6060 calls for shorter chunks of noninterrupted grinding too. Just thinking aloud... -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
