Service memory limits#

The practical memory limit will always be less than the service physical memory limit.

All services are subject to operating overhead:

  • A small amount of memory is required by the operating system kernel to manage system resources, including networking functions and disk buffers.

  • Aiven’s cloud data platform requires memory to monitor availability, provide metrics, logging and manage backups.

  • Services may utilize optional components, service integrations, connection pooling, or plug-ins that also consume system resources.

In most instances, the combined overhead is negligible; however, it is critically important to maintain availability.

If a service consumes too much memory, the operating system, or management layer, including backups and availability monitoring, may fail status checks or operations due to resource contention. In severe instances, the node may fail completely with an Out Of Memory condition.

For database services with unbounded memory allocation, a memory limit is placed on the primary service.

Services with memory limits#

A memory limit is applied to the primary process of the following Aiven services:

  • InfluxDB®

  • MySQL

  • PostgreSQL®

With all new instances, a limit of 80% of available memory (RAM - 350MB) is assigned to the primary process, with the remainder reserved for operating overhead and page cache.


Reserved memory for non-service use is capped to a maximum of 4GB.


For MySQL, a minimum of 600MB is always guaranteed.