How to interpret it
The base peak adds global buffers and every per-connection buffer. It does not mean MySQL allocates it all at startup; it shows the commitment the configuration can make under concurrency.
Tool for DBAs
Model global buffers, per-connection costs, and temporary tables for every MySQL and MariaDB generation before changing production configuration.
1. Enter your configuration
All sizes are in MiB.
2. Compare with RAM
The planning budget uses 70% of RAM.
3. Validate under load
This is a model; verify with production metrics.
The base peak adds global buffers and every per-connection buffer. It does not mean MySQL allocates it all at startup; it shows the commitment the configuration can make under concurrency.
On MySQL 8+, tmp_table_size limits each internal temporary table and temptable_max_ram controls global TempTable use. Do not blindly multiply tmp_table_size without checking those limits and query behavior.
Confirm effective values with SHOW VARIABLES, observe real connection concurrency, and validate host memory use. Tuning should reduce measurable risk, not just increase buffers.
From calculation to real operations
This calculator is an estimate for MySQL and MariaDB. PG Monitoring specializes in PostgreSQL and applies the same capacity discipline with real telemetry, not static assumptions.
Assisted diagnostic: we never request passwords or connection strings through forms, email, or WhatsApp.
What the SaaS tracks in PostgreSQL
Use RAM effectively available to the process, not all physical host memory. This calculator reserves 30% for the operating system, page cache, and unmodeled spikes.
No. The limit does not allocate everything at startup, but it defines how many connections can request per-connection buffers concurrently and therefore the capacity worst case.
Modern MySQL uses TempTable with a global budget such as temptable_max_ram. MariaDB uses per-connection temporary-table limits such as tmp_memory_table_size and max_heap_table_size.
No. Query Cache was removed in MySQL 8. It still exists in MariaDB, but should be evaluated carefully because of lock contention.
Technical references: MySQL documentation on memory use and TempTable, and MariaDB documentation on memory allocation. This tool is a planning model, not a replacement for load testing or process observability.