MySQL InnoDB and Low-Memory Host Integration: Buffer Pool Sizing

Optimizing a MySQL 8.0 deployment for low-traffic workloads requires balancing memory footprints against the risk of disk swapping. When integrating MySQL into a resource-constrained environment, such as a small container or a shared VPS, the innodb_buffer_pool_size must be tuned to prevent the host OS from triggering the OOM killer.

There is a technical uncertainty regarding the minimum viable buffer pool size for small datasets that still maintains acceptable performance during occasional traffic bursts. Reducing this value aggressively minimizes operational costs but may increase I/O wait times due to frequent page evictions.

• What is the recommended minimum innodb_buffer_pool_size for a low-traffic workload to avoid excessive disk swapping?
• How does the interaction between a reduced buffer pool and the innodb_flush_log_at_trx_commit setting affect overall I/O overhead in these environments?