An example from practice inspir me to write this article. The sad truth today is that users using a MySQL database today have no idea what it is or how it works. Thanks to the fact that WordPress runs on 40% of all websites and as for CMS, its market share is almost 65%, so there is nothing to be surpris about.
It all start with a simple customer request. It went something like this: “I’ve done all the database optimizations, but the number of posts on my site is so large that it can’t be handl anymore. Please, can you help me in any way?”. A quick look at the database show me that he was right. Database over 2GB in size, number of contributions over 450,000. What about that?
Since its inception, MySQL has us MyISAM as a database engine. It was fast to read, support full-text search, just perfect for the web decades ago. This has been outdone for a few years and has been gradually replac by the InnoDB repository, mainly thanks to the support of transactions, foreign keys and, last but not least, row-level locking.
As time went on, alternativ
atabase repositories gradually made their way into offshoots of the original MySQL (own by Oracle). I’m not going to go over them all, but let’s look at two of them.
TokuDB
TokuDB is a database repository where the most interesting thing is that it uses Fractal tree indexes for keys. This achieves up to 20x more performance compar to InnoDB (uses B-tree indexes) with much less memory demand. So if you have huge data on a fairly load database, this storage can significantly spe up the response of your applications. It can do everything InnoDB does, including foreign key support.
RocksDB
RocksDB was develop by Facebook indonesia phone number data when InnoDB was no longer enough. Key features are spe and minimal disk requirements. It supports transactions, but not foreign keys.
How do I know if I have RocksDB or TokuDB
on my server? The SHOW ENGINES command is sufficient for let’s expand on the above this; in the mysql console or in phpMyAdmin tab Storage. If the storage type is not there, it nes to be install. If you are using MariaDB, see the installation procure at
If you are using Percona Server for MySQL, so the installation procure can be found at
Warning!!!
While ALTER TABLE command `wp_postmeta` ENGINE = TokuDB; it work for me without problems on a 1.5GB table, so the command ALTER TABLE `wp_postmeta` ENGINE = ROCKSDB; caus the server to crash (5GB of free space was not enough for this operation).
So I recommend exporting the bw lists table (or the entire database) and replacing .