<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MariaDB on The Blog of Boban Acimovic</title><link>https://acim.net/tags/mariadb/</link><description>Recent content in MariaDB on The Blog of Boban Acimovic</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>The Blog of Boban Acimovic &amp;copy; 2026</copyright><lastBuildDate>Sat, 26 Dec 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://acim.net/tags/mariadb/index.xml" rel="self" type="application/rss+xml"/><item><title>Automated MySQL MariaDB tables optimization in Kubernetes</title><link>https://acim.net/blog/automated-mysql-mariadb-tables-optimization-in-kubernetes/</link><pubDate>Sat, 26 Dec 2020 00:00:00 +0000</pubDate><guid>https://acim.net/blog/automated-mysql-mariadb-tables-optimization-in-kubernetes/</guid><description>&lt;p&gt;Kubernetes simplified applications management a lot and this also applies to databases like MySQL/MariaDB, but lot of DevOps forget to apply traditional maintenance and optimization which is still necessary unless you are using some &lt;a href="https://operatorhub.io/" target="_blank" rel="noopener"&gt;operator&lt;/a&gt;
 capable of doing so. The optimization method that will be described here applies just to single and master-slave replicated MySQL/MariaDB instances. If you run some clustered version like &lt;a href="https://galeracluster.com/" target="_blank" rel="noopener"&gt;Galera&lt;/a&gt;
, you probably have to find another way because of possible consistence and performance problems during the eventual optimization. This method would still work but you may have unpredictable consequences.&lt;/p&gt;</description></item></channel></rss>