Recently, I’ve upgraded the database of this blog from MySQL to MariaDB.<\/p>\n
For those of you who are not aware, MariaDB is a fork from MySQL by the original founder of MySQL.
\nMariaDB 5.5 is fully compatible with MySQL 5.5 and can be replaced by “dropping in” directly over MySQL.<\/p>\n
What I noticed after upgrading to MariaDB was that the memory usage shot up to close to my VPS limit.
\nAs my VPS has limited memory, this sudden memory increase might create problems down the road.<\/p>\n
After investigating the possible causes, it was traced to the new database engine introduced in MariaDB, the Aria Storage Engine.<\/p>\n
According to the Knowledge Base<\/a>, the default buffer size is 128M, a pretty big number for a VPS with only 512M of available memory. There, after tuning the buffer size to 512K and 16K, the memory usage is back to normal.<\/p>\n","protected":false},"excerpt":{"rendered":" Recently, I’ve upgraded the database of this blog from MySQL to MariaDB. For those of you who are not aware, MariaDB is a fork from MySQL by the original founder of MySQL. MariaDB 5.5 is fully compatible with MySQL 5.5… Continue Reading
\nSince I’m still using the ISAM engine and have no need to use the Aria engine, it should be turned off to reduce the memory usage.
\nHowever, as the storage engine is an integral part of the DBMS, it couldn’t be turned off, so the next best thing would be to tune the config in my.cnf<\/p>\n\n[mariadb]\naria_pagecache_buffer_size = 512k\naria_sort_buffer_size = 16k\n<\/pre>\n