InnoDB allows you to make multiple INSERT and also UPDATE without creating LOCKING , while in MyISAM it is not possible to make multiple INSERTs at the same time and to make matters worse MyISAM does not support TRANSACTION . >
However, InnoDB seems to store all the data in RAM while MyISAM stores only the indexes, which is a good saving of RAM.
My problem:
Many tables are records as if they were a "Log", that is every transaction that the user does is registered and this logically can not be deleted in any moment, however it is rare situations where there is some SELECT , there are tables where 90% of the time is only written.
For this reason InnoDB is used because there are many and many writings and rollbacks. However the InnoDB RAM system requires a lot of RAM, in which case it would not be necessary because there is little SELECT. I believe that the use of RAM is required when there is a lot of SELECT, so the indexes and content would already be available on time. But in that case it is wasteful.
Meanwhile there are tables that there are many writes and readings, which are affected by lack of memory.
PS: The server has 64GB of RAM and is unique to MariaDB
Is there any alternative engine to InnoDB / XtraDB for MariaDB 10.1?