Vini Engel skrev, on 05-08-2007 19:13:
[....]
Also, you may want to consider changing the dspam tables from MyISAM
to InnoDB. InnoDB is more transaction-oriented and will likely be
faster in this case, due to row-level locking vs. MyISAM's table-level
locking. The locking issue is particularly important when you have a
lot of dspam processes all competing for the same tables, which it
sounds like you do.
Thanks for this tip, this sounds like something that will help me. I
will make those changes this week and will post the results here.
To my mind, InnoDB should be the standard for MySQL. However, the (only
that I know of) downside is, that one'll never reclaim DB space as one
can with MyISAM tables, even by reconverting tables to MyISAM or
dropping a database and recreating it.
Just installed a new RHL5 mail server with MySQL 5.0.22 and imported the
old server's SQL dumps; the old server's ibdata1 was 15 GB, that of the
new is 140 MB. Why? because I was so stupid as to use a per-user dspam
setup on the old one. I then changed to a shared group on the old one
and tried to claim the space back. But whatever I did (like converting
tables back to MyISAM and optimizing, or whatever) had no effect on the
15GB. Still, I didn't know any better ...
--Tonni
--
Tony Earnshaw
Email: tonni at hetnet dot nl
