This is not an article with lot of bar charts. I am no database expert but I can talk something about database which so called some “WordPress Experts” in their “professional services” possibly has no such options to the clients. Slow WordPress is quite common and blindly increasing RAM like work is not a solution. Talking about InnoDB vs Percona XtraDB vs TokuDB Storage Engine for WordPress is a Need. Our guides makes Percona XtraDB enabled by default, we are talking about guides like installing WordPress Nginx on Ubuntu 16.04LTS (which is officially suggested guide on WordPress documentation for Nginx PHP7-FPM). In older publications on this website we discussed about why to shift towards InnoDB from MyISAM, how to optimise InnoDB, how to utilise caching on InnoDB etc. If you know nothing, a complete n00b – InnoDB, Percona XtraDB, TokuDB are storage engine of MySQL servers. Original MySQL has various forks and most known are Original MySQL, MariaDB and Percona. We use Percona as Percona has hundreds of advantages like official paid support with same software. Percona XtraDB storage engine is patched version of InnoDB. We say “InnoDB” instead of saying “Percona XtraDB” as later is more practical, when we are not talking about one website, one database server on same web server. Running database server on hardware without much calculation itself a bottleneck. If you are :
- using our any guide published after 2015, then all are Percona XtraDB enabled
- using our any guide published after 2015, then all are InnoDB enabled (just a matter of name to a n00b)
- using Percona MySQL server with innodb directives from guides other than us then then all are Percona XtraDB hence InnoDB enabled
- trying to optimise or experiment then take backup
We have not talked about TokuDB so far before.
InnoDB vs Percona XtraDB vs TokuDB Storage Engine For WordPress
Under normal circumstances, tuning Percona Server’s InnoDB aka XtraDB should be enough to deliver good performance. TokuDB is not exactly “mainstream”. After login to MySQL Server, if we run :
---
1 | show engines; |
that returns some read only information around the engine under use.
1 | show plugins; |
will return some read only information around the installed plugins. Now, at this point one must take backup of database, test that backup and then proceed. We think to migrate from InnoDB to TokuDB only on cluster, not single server.
These are helpful guides to install TokuDB for Percona:
1 2 | https://www.percona.com/doc/percona-server/LATEST/tokudb/tokudb_installation.html https://www.percona.com/blog/2014/06/26/percona-server-with-tokudb-beta-installation-configuration/ |
Likewise, for MariaDB the command to install TokuDB is like :
1 | INSTALL SONAME 'ha_tokudb'; |
The file /etc/mysql/conf.d/tokudb.cnf will need to have settings like :
1 2 3 4 5 6 7 8 9 10 11 12 | [mariadb] #plugin-load=ha_tokudb.so tokudb_cache_size=300GB tokudb_commit_sync=off tokudb_fsync_log_period=1000 tokudb_directio=ON tokudb_disable_slow_alter=ON tokudb_disable_hot_alter=OFF tokudb_load_save_space=ON tokudb_row_format=tokudb_fast |
Then restart MariaDB.
1 2 3 | MariaDB [(none)]> use target_database-name; Database changed MariaDB [target_database-name]> alter table user_data engine=tokudb; |
InnoDB is easy name for MariaDB or whatever’s Percona XtraDB and TokuDB is definitely not for the n00b. That is difference. Obviously TokuDB has some positive points as from point of performance otherwise would not be developed as new thing.
But for who do not need cluster, Percona with optimised InnoDB/XtraDB is enough for WordPress. That is what we written as guides where question of “official” arises.
Tagged With paperuri:(d132a67b3bdeb3dc8e2be1ffda323bcf) , percona tokudb tutorial , tokudb extradb innodb , tokudb vs xtradb , XtraDB and InnoDB