Print Page | Close Window

Mysql tuning for SpamFilter

Printed From: LogSat Software
Category: Spam Filter ISP
Forum Name: Spam Filter ISP Support
Forum Description: General support for Spam Filter ISP
URL: https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=4648
Printed Date: 12 December 2025 at 9:51am


Topic: Mysql tuning for SpamFilter
Posted By: Guests
Subject: Mysql tuning for SpamFilter
Date Posted: 28 November 2004 at 12:23am

Hello,

I have been trying to use Mysql with SF and I have gotten it to work; however, I have some problems.  When I first tried it my database would get corrupted, I looked up some tuning information and have gotten it not to corrupt that database.

Now my biggest problem is that Mysql spikes my CPU at 100% every second or so.  This is on a Windows 2000 computer with 1GB memory.  Does someone have a my.cnf they can share that works best with SF and Windows 2000?

 


Replies:
Posted By: Guests
Date Posted: 29 November 2004 at 10:29am

Okay here is what I found out on my own so far.

I have SF running on a Windows NT server with 512MB RAM with a 2.4Ghz processor.  The MySQL server is a Windows 2000 with 1GB RAM with a 2.6Ghz processor.

Both servers would spike to 100% CPU usage and sometimes stay at the 100% CPU and sometimes start consuming all RAM.  I tried tuning the MySQL settings which made little to no difference.  Even after optimizing the database did not help. 

I emptied the database tables (tblmsgs and tblquarantine) and both problems went away (once I stopped and restarted the SF service).  The optimized database was 1.5GB before I emptied the tables.  My quess would be a corrupted index or I need a better index in the database?  Is there something that would help with this?  A command I should run daily on the MySQL quarantine database or a setting on MySQL that I should have.  This has happened several times now and emptying the database seems to be the only solution each time.

 

 

Posted By: Guests
Date Posted: 29 November 2004 at 2:51pm
Okay more information on MySQL going wacko with SF.  In looking at the "Handler_read_rnd_next" status I find I get several million after only running for about an hour.  I did a web search and this is what I found:
 
Handler_read_rnd_next
The number of requests to read the next row in the data file. This will be high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have.

So my question is what can I do to either create an index that SF will use to make it better or some setting I need to change in SF?

 


Print Page | Close Window