MariaDB

Optimize MariaDB 10.11 Performance on a 1GB RAM Ubuntu VPS (Native Configuration)

Philip Jensen

— 3 min read

Optimize MariaDB 10.11 Performance on a 1GB RAM Ubuntu VPS (Native Configuration)

At ByteHosting, we understand that running a database like MariaDB on a low-memory VPS can be challenging. With only 1GB of RAM, every resource counts, and proper tuning is essential to ensure your database performs efficiently without external tools. In this guide, we’ll walk you through native configuration tuning for MariaDB 10.11 on an Ubuntu 24.04 VPS, helping you maximize performance while keeping resource usage in check.

Prerequisites: Fresh Ubuntu 24.04 VPS with MariaDB Installed

Before we begin, ensure you have a clean Ubuntu 24.04 server with MariaDB 10.11 installed. If you haven't installed MariaDB yet, you can do so with the following commands:

sudo apt update
sudo apt install mariadb-server

Our goal is to optimize this setup for a 1GB RAM environment, so no additional external tools or heavy monitoring software are necessary. Just a basic installation and native configuration adjustments.

Understanding MariaDB Performance Parameters

MariaDB’s performance depends heavily on its configuration parameters. Key settings include buffer sizes, cache limits, and thread handling. On a low-memory VPS, we need to reduce these values to prevent swapping and ensure the server remains responsive.

Some critical parameters to consider are:

  • innodb_buffer_pool_size: Controls the size of the InnoDB buffer pool. For 1GB RAM, allocate a small portion, typically 50-70MB.
  • key_buffer_size: Used for MyISAM indexes. Set it to a few megabytes, e.g., 8MB.
  • query_cache_size: Cache for query results. On modern MariaDB versions, it's often disabled for better performance, but on low-memory, a small size (e.g., 2MB) can help.
  • max_connections: Limit the number of simultaneous connections to reduce memory usage, e.g., 10-20.
  • thread_cache_size: Cache threads to reduce overhead, set to 4 or 8.

Editing my.cnf for Low-Memory Optimization

MariaDB’s main configuration file is located at /etc/mysql/mariadb.conf.d/50-server.cnf. We’ll edit this file to apply our tuning parameters. Always back up the original before making changes:

sudo cp /etc/mysql/mariadb.conf.d/50-server.cnf /etc/mysql/mariadb.conf.d/50-server.cnf.bak

Open the file with your preferred editor:

sudo nano /etc/mysql/mariadb.conf.d/50-server.cnf

Locate the [mysqld] section and add or modify the following parameters:

[mysqld]
# Basic settings for low-memory environment
innodb_buffer_pool_size = 64M
key_buffer_size = 8M
query_cache_size = 2M
max_connections = 10
thread_cache_size = 4

# Disable query cache if not needed
query_cache_type = 0

# Reduce table cache
table_open_cache = 64

# Limit sort and join buffers
sort_buffer_size = 1M
join_buffer_size = 1M

Save and close the file. These settings are conservative but should significantly improve performance on a 1GB VPS.

Applying and Testing Configuration Changes

To apply the new configuration, restart MariaDB:

sudo systemctl restart mariadb

After restarting, verify that the settings are active:

mysql -e "SHOW VARIABLES LIKE 'innodb_buffer_pool_size';"
mysql -e "SHOW VARIABLES LIKE 'key_buffer_size';"

Monitor the server’s resource usage with:

top -o %MEM

This helps you see if MariaDB is consuming an acceptable amount of memory and if the system remains stable.

Monitoring MariaDB Performance and Resource Usage

Regular monitoring is crucial. Use built-in tools like SHOW STATUS to check query performance and cache hit rates:

mysql -e "SHOW STATUS LIKE 'Qcache_hits';"
mysql -e "SHOW STATUS LIKE 'Qcache_inserts';"

Additionally, keep an eye on system memory and CPU usage with htop or free -m. If you notice high swap usage or CPU bottlenecks, revisit your configuration and reduce buffer sizes further.

Adjusting Settings Based on Workload

Every workload is different. If your database handles mostly read operations, you might increase the query cache size slightly. For write-heavy workloads, keep buffers small to avoid excessive memory consumption.

Experiment with the following adjustments:

  • Increase innodb_buffer_pool_size gradually if you have more free memory, but stay within safe limits.
  • Reduce max_connections if you see many idle connections consuming resources.
  • Enable slow query logging to identify and optimize slow queries.

Troubleshooting Common Performance Issues

If you experience slow responses or high resource usage, consider these steps:

  1. Check for slow queries with SHOW PROCESSLIST and optimize them.
  2. Ensure your server isn’t swapping; if it is, reduce buffer sizes further.
  3. Review error logs for warnings or errors that might indicate misconfiguration.
  4. Limit the number of active connections to prevent memory exhaustion.

Conclusion

Optimizing MariaDB 10.11 on a 1GB RAM Ubuntu VPS requires careful tuning of configuration parameters to balance performance and resource constraints. By editing the my.cnf file with conservative values, monitoring resource usage, and adjusting based on workload, we can achieve a responsive and efficient database environment. At ByteHosting, we’re committed to providing reliable, affordable VPS hosting solutions that support your technical needs. Whether you’re running a small website or a development environment, native configuration tuning is a cost-effective way to get the most out of your server.

Read more