ProxySQL 2.7 → 3.0: roughly 4× faster cache audits in PmaControl
From 8.112 to 2.015 ms per cache audit: ProxySQL 2.7.3 versus 3.0.5, PmaControl measurements, Ubuntu 24.04 methodology, downloadable data and graphics.
Read article →
From 8.112 to 2.015 ms per cache audit: ProxySQL 2.7.3 versus 3.0.5, PmaControl measurements, Ubuntu 24.04 methodology, downloadable data and graphics.
Read article →Why MariaDB replication mechanisms are not enough to manage MySQL 8.4, and how a dedicated MaxScale monitor handles Source/Replica syntax, UUID GTIDs, failover, and rejoin.
Read article →Making PmaControl's chunked time-series inserts atomic was expected to cost a little. The benchmark says otherwise: 12.5% faster ingestion. Here's why.
Read article →Field note: switching to GTID does not purge source binlogs, but CHANGE MASTER resets the replica local relay logs.
Read article →Full recap of the April 2026 sprint: MySQL 8.4 compatibility, binlog analysis, GeoIP IPv6, UI redesign, ReadOnly role, and the roadmap ahead.
Read article →New PmaControl feature: analyze master binlogs directly from the UI to diagnose MySQL/MariaDB replication lag causes.
Read article →Complete guide to setting up MariaDB / MySQL replication and monitoring it in PmaControl: lag, GTID, corrective actions.
Read article →Complete installation guide for MySQL 8.4 LTS on Debian 13 trixie — Oracle APT repository, hardening, configuration, datadir, performance_schema.
Read article →How PmaControl leverages performance_schema to identify slow queries, missing indexes and optimize your MariaDB / MySQL servers.
Read article →How PmaControl handles multi-source replication: channel detection, independent monitoring, limitations and roadmap.
Read article →Aggregate multiple MySQL sources into a single multi-source replica with MySQL 8.4 — complete guide.
Read article →MySQL 8.0 renamed Master/Slave to Source/Replica. Here's how PmaControl and the Glial framework handle bidirectional compatibility.
Read article →MyISAM is officially deprecated: the mysql system database and temporary tables have migrated. Why and how to abandon MyISAM for good.
Read article →MariaDB's history since the 2009 fork: technical divergence, dual Foundation/Corporation governance, massive adoption and continuous innovation.
Read article →