System Variable Differences Between MariaDB 5.5 and MySQL 5.5
The following is a comparison of variables that either appear only in MariaDB 5.5, or have different default settings in MariaDB 5.5, and MySQL 5.5. MariaDB and MySQL 5.5.38, with only default plugins enabled, were used for the comparison.
The most notable differences are that MariaDB includes, by default, the Aria storage engine, uses Percona's XtraDB instead of Oracle's InnoDB, and has a different thread pool implementation. For this reason, a default implementation of MariaDB 5.5 will use more memory than MySQL 5.5. This can be handled with the following rules of thumb:
If you are not using MyISAM and don't plan to use Aria:
Set key_buffer_size to something very low (16K) as it's not used.
Set aria_pagecache_buffer_size to what you think you need for handling internal tmp tables that didn't fit in memory.
Normally this is what before you had set for key_buffer_size (at least 1M).
If you are using MyISAM and not planning to use Aria:
Set aria_pagecache_buffer_size to what you think you need for handling internal tmp tables that didn't fit in memory.
If you are planning to use Aria, you should set aria_pagecache_buffer_size to something that fits a big part of your normal data + overflow temporary tables.
The large number of differences between MySQL's and MariaDB's default innodb* variables (based upon InnoDB/XtraDB differences) are not listed here. Details can be found on the MariaDB versus MySQL - Compatibility page.
-
Comma-delimited list of directories in the data directory that are not considered as database directories. Only introduced in MySQL 5.6
134217728
8388608
Size of the buffer for the index blocks used by MyISAM tables and shared for all threads.
admin, filesort, filesort_on_disk, full_join, full_scan, query_cache, query_cache_miss, tmp_table, tmp_table_on_disk
-
For slow query log filtering.
''
-
Controls information to be added to the slow query log. See also Slow Query Log Extended Statistics.
OFF
-
Verify binlog checksums when reading events from the binlog on the master.
4294967295
4294967295 (32-bit) or 18446744073709547520 (64-bit)
The most key seeks required when searching with an index, regardless of the actual index cardinality. If this value is set lower than its default and maximum, indexes will tend to be preferred over table scans.
4294967295
4294967295 (32-bit) or 18446744073709547520 (64-bit)
Read lock requests will be permitted for processing after this many write locks.
262144
-
Size of buffer to use when using multi-range read with range access. See Multi Range Read optimization.
new
-
OFF
Used for backward-compatibility with MySQL 4.1, not present in MariaDB
Empty string
-
Used for getting MariaDB to emulate behavior from an old version of MySQL or MariaDB. See OLD Mode.
A series of flags for controlling the query optimizer. MariaDB has introduced a number of new settings.
OFF
-
Whether to strip any comments from the query before searching to see if it exists in the query cache.
OFF
-
Tells the slave to reproduce annotate_rows_events received from the master in its own binary log.
ON
-
Verify binlog checksums when the slave SQL thread reads events from the relay log.
Number of processors
16*
See Using the Thread Pool in MariaDB 5.5. *Only available in MySQL with a commercial plugin.
See Also
Last updated
Was this helpful?