Should I use MyISAM over InnoDB to save disk space? I have a table that consists of an int primary key and text column and serving primarily in a &quot;read&quot; role. There are currently only about 40,000 rows, but in time, I expect there to be an additional 500,000 rows per year. This is on a system with perhaps 10 active users per day, so very low-impact.
With MyISAM, the table is less than 4MB. With InnoDB, it is over 7MB.
If disk space is a concern, is MyISAM really so untrustworthy that I should use InnoDB over MyISAM?
You're worried about 3MB? er- don't.
Even at 10x that, roughly your expected increase, it would be 30M.
You aren't going to get saving of 30M of storage to counter any reliability failure.
Use InnoDB.