0

I have a table that consists of an int primary key and text column and serving primarily in a "read" 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?

3
  • Its the year 2021 and you're worried about 3MB? Even at 10x that, it would be 30M. You aren't going to get saving of 30M of storage to counter any reliability failure. Use InnoDB. – danblack Feb 17 at 5:34
  • Growth projections put us out to ~500MB to 1TB in five years. – pbarney Feb 17 at 17:33
  • 1
    And in 5 years you won't be able to buy a disk that is only 1TB ! – Rick James Feb 18 at 23:34
1

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.

2
  • Is there any point in storage savings where you would be inclined to use MyISAM at all? Does 1TB give you any pause? – pbarney Feb 17 at 17:34
  • growth implies you are writing to it, and need durability. – danblack Feb 17 at 21:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.