On 6/23/08, Fletcher Cocquyt wrote:
(and yes the spamassassin checks are the source of the 4-10 second delay -
now those happen in parallel x16 - so no spikes in the backlog...)
Search the FAQ for "performance". Do all such spam/virus/DNS/etc...
checking up front, and run a second copy of
Mike, many thanks for your (as always) very helpful response - I added the 1
liner to mm_cfg.py to increase the threads to 16.
Now I am observing (via memory trend graphs) an acceleration of what looks
like a memory leak - maybe from python - currently at 2.4
I am compiling the latest 2.5.2 to see
Fletcher Cocquyt wrote:
Hi, I am observing periods of qfiles/in backlogs in the 400-600 message
count range that take 1-2hours to clear with the standard Mailman 2.1.9 +
Spamassassin (the vette log shows these messages process in an avg of ~10
seconds each)
Search the FAQ for performance. The
Fletcher Cocquyt wrote:
>Hi, I am observing periods of qfiles/in backlogs in the 400-600 message
>count range that take 1-2hours to clear with the standard Mailman 2.1.9 +
>Spamassassin (the vette log shows these messages process in an avg of ~10
>seconds each)
Is Spamassassin invoked from Mailm
Hi, I am observing periods of qfiles/in backlogs in the 400-600 message
count range that take 1-2hours to clear with the standard Mailman 2.1.9 +
Spamassassin (the vette log shows these messages process in an avg of ~10
seconds each)
Is there an easy way to parallelize what looks like a single ser
