use Perl

• Shouldn't happen (Score:3, Informative)

  by Matts (1087)

  If it's happening it's a bug. Find out what mails caused it to slow down and submit a bug report and attach the mails in question.
  
  And turn off network checks. They can be very slow.
  
  And make sure you're using the latest release. There are often a number of timeout (network check related) fixes in each release. And we test the other rules extensively for performance issues.
  
  SpamAssassin is slow, but it really shouldn't kill your box.
  • Re:Shouldn't happen (Score:1)

    by ethan (3163) <reversethis-{ed. ... rap.nov.olissat}> on 2003.05.22 8:17 (#20406) Journal

    If it's happening it's a bug. Find out what mails caused it to slow down and submit a bug report and attach the mails in question.
    
    Oh, that didn't even occur to me. I'll try to watch spamassassin more carefully and see whether particularly slow runs can be pinned down on certain messages. This morning I had the impression that it was simply due to the fact that about 100 messages were to be processed (in 'top' one spamd process was quickly replaced by a new one; so each single run appeared to be pretty fast).
    
    And turn off network checks. They can be very slow.
    
    I'd really love to keep those turned on because they catch a lot of spam. With the tweak of my procmailrc I might have cleared the most obvious bottle-neck.
    
    Btw: I am using 2.54...2.55 is more recent but it allegedly has only a few cosmetic changes targeted towards (mainly) older perls.

    Reply to This

    Parent

    • Re:Shouldn't happen (Score:2)

      by Matts (1087)

      Another thing to try is leave on the network checks that work well, and turn the rest off (set their score to zero).
      
      I'd list the ones I think you should leave on, but I'm lazy :)