Linux RAM sizing recommendation outside of Aerospike

The Aerospike Knowledge Base has moved to Content on is being migrated to either or Maintenance on articles stored in this repository ceased on December 31st 2022 and this article may be stale. If you have any questions, please do not hesitate to raise a case via


Recommended RAM provisioning for Linux OS ressources after having properly sized for Namespace Indexes, Secondary Indexes, and Namespace Data (if data is in RAM).


As a general guideline we recommend reserving 10-15% of the total physical memory for Linux system ressources. Experience has shown us that this value will help avoid OOM issues. This recommendation is to take account for memory fragmentation, Linux and services, and Aerospike RAM not used by the Namespace/Secondary Indexes.


Be sure to properly size all components that influence memory:

  1. Overhead from Linux and services.
  2. Overhead caused by memory fragmentation.
  3. Overhead from Aerospike indexes (primary & secondary), and Namespace data for data-in-memory namespaces. Please see our capacity planning doc.(
  4. Overhead from cache and queue related configurations including max-write-cache (per device) and post-write-queue (per device).
  5. Overhead from the Aerospike process .