On 10/25/07, Ítalo Rossi <[EMAIL PROTECTED]> wrote: > -rw-rw---- 1 mysql mysql 8.6K 2007-06-14 09:00 dspam_token_data.frm > -rw-rw---- 1 mysql mysql 4.1G 2007-10-25 10:16 dspam_token_data.MYD > -rw-rw---- 1 mysql mysql 5.2G 2007-10-25 10:59 dspam_token_data.MYI
You've got huge index file for dpam_token_data. Try to keep this file down. Note that on slow IO (non-raid) it can be too late for online optimization as optimizing the table could last MANY hours and has to be done on an offline copy (provided you can afford loosing training from one weekend). If you have enough RAM, you'll gain quite a speedup for production traffic giving mysql more memory for key buffer (key_buffer_size). And yes, do read about mysql optimization. Oh, one more thing - make sure you used the "speed" version of dspam installation scripts and not the "size" ones. You should not have any field of type varchar (it chould be char to keep static record size). If you have varchars (and comparing index vs. data file sizes, I assume you do), just modify the table structure (again, you'll block dspam for a while with this operation). -- greets, bm.
