Kris Deugau wrote:
Steven W. Orr wrote:
I. I am running MySQL version 5.067 which apparently is not enough to be
allowed to run InnoDB.
Strange; IIRC InnoDB has been available since some late 3.something
versions, and most 4.x releases. The MySQL docs should be the
authoritative reference for this though.
Yes, up to my knowledge MySQL 5.0.xx supports InnoDB just fine.
The questions is this: I thought that InnoDB was going
to consume *more* resources because the purpose of it was to support
transactions. Am I wrong? If I convert to a higher rev of MySQL and
get InnoDB
will I get *better* performance?
Likely not; MySQL gets a great deal of its speed from... not doing
transactions.
Not having done any detailed performance tuning or testing, I can't
say for sure - but from what I recall from my reading on this subject
that's one of the points formally documented by the MySQL devs
themselves.
I can tell from experience that MyISAM is useless when it comes to
Bayes. As pointed out by Benny Pedersen, MySQL will do nothing more than
waiting on table locks. A single UPDATE query will take 30-90 seconds,
and even more when you are on a busy site, not to mention the load of
your MySQL server is going skyhigh. Your scantimes will increase
dramatically to over 2-3 minutes of a single e-mail. If you, like me,
get 25.000 emails a day to process you can't afford this.
Using InnoDB is absolutely vital and you cannot use MyISAM at all from
my experience. My bayes_token table is 12 million rows and increasing
every day, and performance is still just fine.
Hope this helps some.
Jorn
