1) We use innodb and our current databases exceeds 200 GB. We do have
a lot of operations on the tables which is the primary reason to use
innodb. myisam locks the table on certain operations. ;-) We were not
so concerned about ACID.
2) I recommend you guys check out mysqlperformanceblog.com. They have
a ton of tips to tune innodb, in general, you will need a lot of ram
as you move forward. It also doesn't hurt to read those tips now
because you won't be able to change certain parameters without
re-importing all your tables. Aside from tips, they also offer a bunch
of useful tools which make dealing with mysql a lot easier.
3) We don't use SQL to search the data, we use an external tool.
That's the #1 argument for myisam -- it's so fast, and fulltext, etc..
All of this is true and fulltext is fine, but it's just not bearable
with a lot of traffic. Just take a look at Apache Solr -- it's a lot
easier to do search with it.
4) Look into the percona (percona is the company who runs the
mysqlperformanceblog, experts in this space) builds of MySQL since
they include a lot of extra patches which generally improve
performance.
5) If I started from scratch now, I'd either ditch mysql all together
and move to an all document-oriented database or at least use xtradb
(innodb-compatible storage engine by percona).
Hope that helps!
Till
没有评论:
发表评论