[Greylist-users] Greylisting with MySql I/O performance

[Jason 'XenoPhage' Frisvold]

Kent Ziebell wrote:

> Anyone seen I/O performance issues with MySql greylisting database?  
> We process roughly 3M pieces of email each week.  We are running our 
> database on a 3Ghz system, and it is running almost 98% idle cpu.
>
> However, the database is on a single IDE disk, and it appears to be 
> running 98-100% busy.  We know we would get some benefit from using a 
> SCSI disk instead, but are wondering if we should move to hardware 
> Raid 0 (striping) instead?

Sounds like it's I/O limited...  Hard drives are too slow :)  Might I 
suggest using a memory table?  Have some process run at 1am and copy the 
memory table to a hard drive table (for backup purposes) ..  You'll 
benefit from speedy lookups and still have a backup (albeit a day old) 
to fall back on...

> We are seeing delays on our mail servers that are inquiring against 
> the greylist database at this point.  Comments?
>
> We have tuned the MySql database as best we can with table-cache set 
> to 1200, max_connections to 300, and key_buffer to 20M.  Any other 
> suggestions?

Memory tables :)

> Also we added an index for record_expires to relaytofrom for the 
> maintenance script that gets run nightly, but it too is taking way too 
> long to run - again I suspect I/O is the problem.

That maintenance script is a killer...

> Thanks,
>
> Kent Ziebell



-- 
---------------------------
Jason 'XenoPhage' Frisvold
Engine / Technology Programmer
friz at godshell.com
RedHat Certified - RHCE # 803004140609871
MySQL Pro Certified - ID# 207171862
MySQL Core Certified - ID# 205982910
---------------------------
"Something mysterious is formed, born in the silent void. Waiting alone and unmoving, it is at once still and yet in constant motion. It is the source of all programs. I do not know its name, so I will call it the Tao of Programming."