---
schema_version: "1"
id: 8d03586402a1d1a29487437cac957cbb030782b31a54697f18dff13416f4e635
title: Resource Sizing for Self-Managed Omni Gateway
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/gateway/1.13/sizing-guide.md
canonical_url: https://docs.mulesoft.com/gateway/1.13/sizing-guide
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 60d0a3ad6f9df1ac8feb796533c2ccd67824555234f116ee722ff99575fb1acf
description: MuleSoft Documentation Site
release: "1.13"
latest: false
---
---
product: Omni Gateway
version: 1.13
---

# Resource Sizing for Self-Managed Omni Gateway

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Before getting started with Omni Gateway, analyze and choose your configuration to obtain the best
performance and auto-scaling rate.

When assigning resources for a replica node, consider:

- Number of APIs

- Amount of memory the node needs

- Processing power for the node

- Number of policies in each API

- Amount of traffic each node handles

- Amount of time the node takes to answer the request (latency)

- Type of traffic the node handles, and within the traffic:

  - The number of requests per second (RPS) the node handles

  - Size of each request (bytes)

## Resources

The following table describes the resources you must allocate to your replica node according to your
environment:

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Node Size</th><th>CPU</th><th>RAM</th></tr></thead><tbody><tr><td><p>Small</p></td><td><p>1-2 cores</p></td><td><p>2-4 GB</p></td></tr><tr><td><p>Medium</p></td><td><p>2-4 cores</p></td><td><p>4-8 GB</p></td></tr><tr><td><p>Large</p></td><td><p>8-16 cores</p></td><td><p>16-32 GB</p></td></tr></tbody></table>

> [!NOTE] For IBM Power10 deployments, allocate 5-16 CPU cores for a "Large" node.

> [!NOTE] Nodes belonging to a cluster must be of the same size.

## Cluster Size

The following table describes appropriate node and cluster sizes:

<table><colgroup><col> <col> <col> <col> <col> <col></colgroup><thead><tr><th>Node Size</th><th>Number of APIs</th><th>Number of Policies</th><th>Expected Latency</th><th>Expected Throughput</th><th>Target Environment</th></tr></thead><tbody><tr><td><p>Small</p></td><td><p>&lt; 100</p></td><td><p>4</p></td><td><p>&lt; 30 ms</p></td><td><p>&lt; 500 RPS</p></td><td><p>Dev/test cluster</p></td></tr><tr><td><p>Medium</p></td><td><p>&lt; 500</p></td><td><p>4</p></td><td><p>&lt; 20 ms</p></td><td><p>&lt; 2500 RPS</p></td><td><p>Production cluster</p></td></tr><tr><td><p>Large</p></td><td><p>&gt; 500</p></td><td><p>4</p></td><td><p>&lt; 10 ms</p></td><td><p>&lt; 10000 RPS</p></td><td><p>Mission-critical clusters</p></td></tr></tbody></table>

These sizing figures are per node. API configurations replicate to all nodes in the cluster. For
example, for 10 APIs deployed each with three policies, the 10 APIs and their policies are deployed
to each node in the cluster.

The traffic is distributed across all nodes in the cluster. A small cluster node supports up to 500
RPS, but if the cluster has two nodes then the total traffic that the cluster allows is 1000 RPS
(500 RPS for each node). Exceeding the recommended traffic per node eventually causes increased CPU
usage. To avoid this issue, you must increase the size of all nodes in the cluster or scale
horizontally.

High CPU usage can lead to increased latency. In such a case, proceed with horizontal scaling or
increase the node size.

High memory consumption can lead to out-of-memory errors. To solve this issue, increase the memory
allocation or the node size. Horizontal scaling might not help solve issues in this situation. You
must increase memory first, and scale horizontally later.

These guidelines are for a cluster with an average request size of 1 KB and four policies
implemented. Adjust your parameters depending on your use case.

The most commonly used out-of-the-box policies are:

- Message logging

- Rate limiting

- JWT validation

- Header injection

Using TLS affects the response time and the process consumption.