Thanks all. I did check 'top' and did increase the memory to 512mb. It's the latest ver of SA so I think it's running only 5 processes. It rarely seems to dip into the swap space, though it does report all the memory as being used so I was assuming it was merely processor time. The CPU was certainly maxed out most of the time. I've removed most of the additional rules and it's back down to 5-6 seconds now, but I'll add them back one by one with a test period in between to see if I can pinpoint what was happening.
I really want this to scale way up from where we are, so I guess a reasonable machine with just loads of ram is the answer? -----Original Message----- From: Loren Wilton [mailto:[EMAIL PROTECTED] Sent: 15 August 2005 10:03 To: users@spamassassin.apache.org Subject: Re: Very long scan times - Finding the culprit rule > back down to 6 secs or so, but it would be very handy to have the actual > times of each test logged so I can see which are the slow ones. Check Top. This sounds a lot like you are thrashing. The rulesemporium rules are fairly carefully written to not be processor hogs, although we have made mistakes in the past. They have typically only showed up when someone had some very strangely formatted mail messages. Now you might indeed have hit some slow or badly composed rules; but I'm betting you are just out of memory. There is a Wiki page by Daniel or Justin or some such on profiling rules. Should be fairly easy to find, and I seem to recall the steps were fairly simple, except they didn't work for me. :-( Loren
