https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6854
--- Comment #2 from AXB <[email protected]> --- (In reply to comment #0) > Created attachment 5102 [details] > The low-hanging fruit > > Spent a day with a NYTProf 4.08 Perl profiler trying to cut down > some of the inefficiencies of SpamAssassin dealing with large mail > messages (which are usually large thanks to some Base64-encoded > attachments). Using Perl 5.16 on a FreeBSD 9.1 platform. > > Picking just the low-hanging fruit with most outstanding hotspots in > each iteration, I managed to shave off about 100 ms of CPU-intensive > hotspots (local tests only) in a command-line spamassassin run > (with a 3 MB message containing a large PDF). > > Depending on what is being measured (like aggregate mail throughput), > and what proportion of large messages are being passed to SpamAssassin > (like passing only the first 420 kB from amavisd to SpamAssassin), > this amounts to between 3 and 7 % of a speedup for large messages. > Not too bad where every bit adds up. I'm not sure I understand: Does Amavisd send chuncks of raw message to SA instead of only the txt/html parts and leave "attachments" unscanned? -- You are receiving this mail because: You are the assignee for the bug.
