2
Innodb allows you to make several INSERT and also UPDATE without creating LOCKING, while in Myisam it is not possible to make several INSERT at the same time and to make matters worse Myisam does not support TRANSACTION.
However, Innodb seems to store all RAM data while Myisam stores only Dexes, which is a huge saving of RAM.
My problem:
Many tables are records as if it were a "Log", this is every transaction that the user makes gets registered and this logically can not be deleted at any time, however it is rare situations where there are 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. But Innodb’s 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 necessary when there is a lot of SELECT, so the Dexes and the content would already be available on time. But in this case it’s a waste.
Meanwhile there are tables that there are many writings and readings, which are affected by lack of memory.
PS: The server has 64GB of RAM and is exclusive to Mariadb
Is there any alternative engine to Innodb/Xtradb for Mariadb 10.1?
You set it up the way you want it. If you want it to take up little memory for each thing, just set it up.
– Maniero
How can I limit consumption from just one table to prioritize another table? Example, two tables "A" with 20GB (with much more reading) and "B" with 30GB (only writing). If the innodb_buffer_pool_size limit is 40GB, how can I make only table "A" use such 40GB?
– Inkeliz
That’s another question entirely different from that, I don’t even know if it can be answered.
– Maniero