Skip to main content

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 cache.
  • Aiven's cloud data platform requires memory to monitor availability, provide metrics, logging and manage backups.

A server (or node) usable memory can be calculated as:

RAMoverhead{ RAM - overhead }


  • overheadoverhead is 350 MiB (≈ 0.34 GiB).

Services may utilize optional components, service integrations, connection pooling, or plug-ins, which are not included in overhead calculations.

If a service is overcommitted, the operating system, management layer, backups or 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.

Services with memory limits

For data services with unbounded memory allocation, a memory limit is placed on the primary service container, with the remainder reserved for overhead and disk cache:

  • MySQL
  • PostgreSQL®

Service memory is calculated as:

(RAMoverhead)×.80(RAM - overhead) \times .80


  • overheadoverhead is 350 MiB (≈ 0.34 GiB).

Reserved memory for non-service use is capped to a maximum of 4 GB. For MySQL, a 600 MB minimum is always guaranteed.