One of the things I’ve been thinking about is how Maria/MyISAM fits into the SSD puzzle WRT InnoDB.
InnoDB was generally designed for use with HDDs. Specifically, the write ahead log was added for MVCC and additional performance.
However, MyISAM on SSD wouldn’t suffer form the same performance hit due to lock contention. At least I don’t think so. I need to run some tests to see if my theory holds.
In high write environments it’s going to lock more but those lock will complete quickly.
So why not ditch InnoDB and just go with MyISAM? InnoDB is a bloated beast compared to MyISAM. Or tables take up about 3.5x additional storage.
SSDs are smaller. About 25x smaller than HDDs (but 30x faster). This means you can fit more than 3x data on the same SSDs.
That, and there are a LOT less IOs that you need to complete – which means 3x additional performance.
The missing piece to the puzzle was crash recovery. If you lose a box due to a hardware problem or core dump how do you get the image back online quickly?
A full restore might work since SSDs are smaller and would be quick to rebuild. The other alternative might be to use Maria since it supports crash recover.
At least there are more options here.