MySQL Database Scalability
summary
Practical MySQL tuning for Nextcloud metadata: use InnoDB, size the buffer pool to 75–80% of RAM with multiple buffer instances tied to CPU cores, and raise innodb_io_capacity for SSDs (default 200 is too low). Beware UUID primary keys because they cause random I/O; prefer auto‑increment for sequential clustering. Query cache helps read‑heavy, low‑write workloads but can bottleneck high‑write systems. For durability tradeoffs set flush_log_at_trx_commit=0/2 to gain write throughput at the risk of losing seconds of recent transactions. Galera adds HA but increases write latency; consider sharding for scale.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:43RAM
- 8:24Performance
- 10:12Performance Patterns
- 12:09What influences read performance
- 21:49What influences the access pattern
- 25:16High availability and performance
- 29:47Single instance vs Galera
