5 ms·
>> We currently use MariaDB, with the InnoDB database engine. It is kind of funny how long InnoDB was the most reliable storage engine. I am not sure if MyISAM
by StreamBright 6y ago
>> We currently use MariaDB, with the InnoDB database engine.
It is kind of funny how long InnoDB was the most reliable storage engine. I am not sure if MyISAM is still trying to catch up, it used to be much worse than InnoDB. With the emergence of RocksDB there are multiple options today.
- kirugan 6y agoMyISAM days are gone, no one will seriously consider it as suitable engine in MySQL.
- jeffbee 6y agoIt is quite likely unless you've meticulously avoided it that MySQL is using ISAM on-disk temp tables in the service of your queries.
- kirugan 6y agoI didn't know that, thanks!
- fipar 6y agoActually, that shouldn't be the case since 5.7: https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_internal_tmp_disk_storage_engine https://dev.mysql.com/doc/refman/5.7/en/server-system-variab... (and related: https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_default_tmp_storage_engine https://dev.mysql.com/doc/refman/5.7/en/server-system-variab...) And on 8 MyISAM is mostly gone, not even the 'mysql' schema uses it. Edit: Originally linked only to default_tmp_storage_engine).
- VWWHFSfQ 6y agoThe only thing I ever used MyISAM tables for was for storing blobs and full-text search on documents. If your data is mostly read only then it's a decent option out of the box. But if you do even mildly frequent updates then you'll quickly run into problems with the table level locking instead of the row level locking offered by InnoDB