MariaDB vs MySQL, in practice

In practice, MariaDB and MySQL are close cousins that speak almost the same SQL. On LogicWeb shared hosting you get MariaDB with cPanel, and most WordPress sites never notice the difference. You should match configs and plugins to the version you actually run, keep that engine patched, and spend your effort on slow queries rather than on the brand name.

Check the version before you paste config

Do not drop a MySQL 8-only setting onto MariaDB and hope it works. Ask the server what it is running first:

mysql -e ‘SELECT VERSION();’

On shared hosting you will usually see a string like 10.6.x-MariaDB. On a VPS you see whatever you installed yourself. That version string is your contract. Optimizer hints written only for MySQL 8 often become comments or errors on MariaDB. If a plugin ships /*+ SET_VAR(...) */ and then fails, that is not a hosting bug. Read the error and adjust the config for the engine you have.

Where MariaDB and MySQL actually differ

They diverge on some JSON functions, a few window-function edge cases, authentication plugins such as caching_sha2_password versus MariaDB defaults, and replica features like GTID flavours or delayed replicas. For a typical WordPress workload, InnoDB behaves like InnoDB on both, and utf8mb4 is utf8mb4. When a vendor says a product “requires MySQL 8,” they sometimes mean a function MariaDB already has, and sometimes they mean Oracle MySQL only. Test on the version you will run in production.

The idea that MySQL is automatically faster is mostly branding. On either engine, a slow shop is usually a heavy query, a missing index, or a bloated autoload in the options table. Pick a supported MariaDB version, keep it patched, and treat the query plan as the real bottleneck.

Replication, dumps, and when to switch

A dump from MariaDB into MySQL 8 often loads cleanly. A dump the other way can fail on a default value, a collation, or a JSON function. Always test the restore on a copy before you cut over. Do not mix engines inside one replica topology just because a blog called them compatible. On a single WordPress node, stay with the engine that came with the image unless you need a named MySQL feature such as a specific auth plugin or replica option.

If the homepage feels slow, check wp_options autoload next rather than debating forks. See our guide on wp_options autoload bloat for the practical next step.