Establishes the least hardware and software resources needed to install and run MariaDB safely.
MariaDB can start on a single-core 64-bit CPU, 1 GB RAM, and 512 MB of free SSD/HDD space. This footprint supports a dev or test instance with light concurrency and small datasets.
MariaDB 10.6+ is certified on 64-bit Linux (Ubuntu 20.04+, RHEL/CentOS 8+, Debian 11+), Windows Server 2016+, and macOS 11+. A 64-bit kernel is non-negotiable; 32-bit systems are unsupported.
Allocate 1–2 MB per idle connection and 4–8 MB per active connection. For 50 active sessions, 1 GB RAM covers the buffer pool, sort buffers, and per-thread overhead.
Yes. SSDs drastically cut fsync latency, so even the minimum disk size (512 MB) should be an SSD for write-intensive workloads. Aim for 100 MB/s sequential write throughput.
Run SHOW GLOBAL VARIABLES and compare innodb_buffer_pool_size to free -m output. Keep buffer_pool ≤70% of physical RAM on a minimal box to avoid swapping.
• 1 vCPU @2 GHz
• 1 GB RAM
• 512 MB free SSD
• 64-bit Linux kernel
• Swap disabled or limited to 512 MB
An ecommerce prototype with Customers, Orders, Products, and OrderItems tables (~1 GB data) runs smoothly on 2 vCPU, 4 GB RAM, and 20 GB SSD. Increase innodb_buffer_pool_size to 2 GB.
Enable slow_query_log, set performance_schema=OFF, and schedule mysqlcheck DDoptimize weekly. These reduce overhead and keep the instance within resource limits.
Yes. A Pi 4 with 2 GB RAM and a fast SD-card or USB SSD meets the minimum spec for dev workloads.
Swap is optional but recommended at 0.5–1× RAM for crash safety. On low-memory systems, disable swappiness to avoid performance hits.
The mysql system schema consumes roughly 80 MB after installation, so allocate at least 512 MB to leave headroom for logs and temp files.