On Thu, Dec 02, 2004 at 04:25:46PM -0300, Matias Lopez Bergero wrote: > > Well, I fix the speed problem that I was having with SA, but I still > have the CPU consumption problem. > > From time to time, some spamd process sticks on top of the top listing > with an ~90% CPU utilization, like this: > > 27639 mselig 39 19 30104 29M 2472 R N 105.2 1.9 60:04 0 spamd > > Here the spamd process is using 105.2% of my CPU resources, and 29MB of > memory. > Normally the spamd process uses between 10 and 30% of CPU resources, the > processes that use around 90% stay there until I kill them. > > There is a way to prevent this?
Possibly. > What can be causing this hi CPU usage? I can't be 100% sure, but I'd put money on bayes expiration, which can be very CPU and IO intensive while it runs. Depending on your setup you could turn off bayes_auto_expire and do the expiration manually (ie sa-learn --force-expire), at a time that you control. Unfortunately, unless you are running a sitewide bayes config, this may not work well with a lot of individual bayes dbs. If you're running 3.0, you could move your bayes databases to SQL which has a much faster expiration time (roughly 7 times faster). This would also allow you to offload some of the CPU and IO consumption to a separate machine. Hope that helps. Michael
pgppPgA9kvTWO.pgp
Description: PGP signature
