---
title: "Gateway Runtime with Four CPUs - Performance Results"
description: "View API Platform Gateway performance benchmark results with a four-CPU gateway runtime, including throughput, average response time, and percentile response times."
canonical_url: https://wso2.com/api-platform/docs/api-gateway/next/performance/gateway-runtime-with-four-cpus/
md_url: https://wso2.com/api-platform/docs/api-gateway/next/performance/gateway-runtime-with-four-cpus.md
tags:
  - api-gateway
  - performance
  - benchmarks
  - gateway-runtime
author: WSO2 API Platform Documentation Team
last_updated: 2026-07-01
content_type: "reference"
---

# Gateway runtime with four CPUs

The table below displays the resource allocations for the gateway-related components deployed as pods on the Amazon EKS cluster used in the performance tests.

| Component          | CPU | Memory | Router Concurrency | GOMAXPROCS |
| ------------------ | --- | ------ | ------------------ | ---------- |
| Gateway Controller | 1   | 2 GB   | —                  | —          |
| Gateway Runtime    | 4   | 2 GB   | 3                  | 1          |

## Throughput (requests/sec) vs. concurrent users

The graph below shows how gateway throughput changes as concurrent users increase for the API without policies and the API with mediation policies.

![Line chart of gateway throughput in requests per second versus concurrent users at 100, 500, and 1000 users, comparing the API without policies and the API with mediation policies on a four-CPU gateway runtime](../../../assets/img/api-gateway/performance/1.2.0/four-core-Throughput-vs-Concurrent-Users.svg){ width="900" }

**Key observations:**

- Maximum throughput for both APIs occurs at 100 concurrent users on this four-CPU configuration.
- Throughput decreases slightly as concurrent users increase beyond 100 due to resource contention.
- Both APIs sustain strong throughput from 100 through 1000 concurrent users on the four-CPU gateway runtime.

## Average response time (ms) vs. concurrent users

The graph below shows how average response time changes for both APIs as concurrent users increase. The backend delay was configured to 0 ms for these tests.

![Line chart of average response time in milliseconds versus concurrent users at 100, 500, and 1000 users, comparing the API without policies and the API with mediation policies on a four-CPU gateway runtime](../../../assets/img/api-gateway/performance/1.2.0/four-core-Average-Response-Time-vs-Concurrent-Users.svg){ width="900" }

**Key observations:**

- Average response time increases as concurrent users grow.
- The four-CPU configuration improves response times compared with the two-CPU results under comparable load.

## Response time percentiles vs. concurrent users

The graphs below show the 90th, 95th, and 99th percentile response times at 0 ms backend delay. Percentile values indicate the response time below which that percentage of requests completed, for example, the 99th percentile is the response time exceeded by only 1% of requests.

![Line chart of 90th, 95th, and 99th percentile response times in milliseconds versus concurrent users for the API without policies on a four-CPU gateway runtime](../../../assets/img/api-gateway/performance/1.2.0/four-core-AP-%20with-8-routes-Response-Time-vs-Concurrent-Users.svg){ width="900" }

**Key observations:**

- 90th, 95th, and 99th percentile response times increase as concurrent users grow.
- The four-CPU configuration yields lower percentile values at high concurrency than the two-CPU configuration.

![Line chart of 90th, 95th, and 99th percentile response times in milliseconds versus concurrent users for the API with mediation policies on a four-CPU gateway runtime](../../../assets/img/api-gateway/performance/four-core-API-with-8-routes-Mediation-Policy-Response-Time-vs-Concurrent-Users.svg){ width="900" }

**Key observations:**

- Percentile trends follow the same pattern as concurrent users increase across the test range.

Test scenario results in CSV format are available [here](https://raw.githubusercontent.com/wso2/api-platform/refs/heads/main/gateway/perf/api-gateway-1.1.0-perf-test-results/four-core-results-summary.csv).