12-04-2007, 07:19 PM
|
#8 (permalink)
|
|
The Contributor
Join Date: Nov 2007
Location: California
Posts: 82
Thanks: 0
|
Quote:
Originally Posted by bluesaga
...
Also, innodb is awesome for writing, but it doesn't allow the benefits that myisam does for reading (fulltext search etc). So it is more beneficial to use innodb as a slave as Adam suggests, and doing an INSERT INTO table SELECT * FROM write_table in order to get an up to date read table!
|
I agree, in my experience with large databases (100+ read/write tables) we'd have double that size in just cached data on MyISAM tables which we ran all of our searches on. yes, the site still gets lots of traffic (i no longer work there), and thousands of searches a day, and worked great off of the caches. (There was load balancing.)
So, my suggestion, is use InnoDB if you have a lot of writes, or want the FK checks, but for the most part, MyISAM is the default recommended table type for a reason. It works as a solution for most of the common problems you'll run into. |
|
|
|