Capacity thresholds, QPS benchmarks, and quota limits for each Cloud-native API Gateway instance specification.
Capacity thresholds
The following table lists capacity thresholds per gateway specification. Full SLA coverage applies when metrics stay below the warning threshold. For critical workloads, keep metrics below the secure threshold.
-
Secure threshold: The gateway maintains high throughput and low latency even if traffic doubles.
-
Warning threshold: Exceeding this level may cause increased latency and stability risks during traffic surges.
-
The
apigw.dev.x1specification is a single-node deployment with no SLA guarantee, intended for testing only. You must use a multi-node specification for production. -
The SLA does not cover request failures when CPU or memory exceeds the warning threshold. The gateway provides alarms for these thresholds. Monitor gateway load and triggered alarms closely.
|
Gateway specification |
Client connections |
New HTTPS connections |
CPU utilization |
Memory usage |
||||
|
Secure threshold |
Warning threshold |
Secure threshold |
Warning threshold |
Secure threshold |
Warning threshold |
Secure threshold |
Warning threshold |
|
|
|
12,000 |
24,000 |
400 |
800 |
30% |
60% |
75% |
75% |
|
|
24,000 |
48,000 |
800 |
1,600 |
30% |
60% |
75% |
75% |
|
|
48,000 |
96,000 |
1,600 |
3,200 |
30% |
60% |
75% |
75% |
|
|
96,000 |
192,000 |
3,200 |
6,400 |
30% |
60% |
75% |
75% |
|
|
192,000 |
384,000 |
6,400 |
12,800 |
30% |
60% |
75% |
75% |
|
|
384,000 |
768,000 |
12,800 |
25,600 |
30% |
60% |
75% |
75% |
|
|
576,000 |
1,152,000 |
19,200 |
38,400 |
30% |
60% |
75% |
75% |
|
|
768,000 |
1,536,000 |
25,600 |
51,200 |
30% |
60% |
75% |
75% |
|
|
1,536,000 |
3,072,000 |
51,200 |
102,400 |
30% |
60% |
75% |
75% |
|
|
2,304,000 |
4,608,000 |
76,800 |
153,600 |
30% |
60% |
75% |
75% |
|
|
3,072,000 |
6,144,000 |
102,400 |
204,800 |
30% |
60% |
75% |
75% |
QPS performance
QPS throughput varies by response size, HTTPS, and gzip compression. The following table lists conservative (worst-case) QPS values per specification at 30% CPU utilization.
New HTTPS connections are CPU-intensive. For workloads with high concurrent HTTPS connection rates, use the short-lived connection data to plan capacity.
|
Specification |
apigw.dev.x1 |
apigw.small.x1 |
apigw.small.x2 |
apigw.small.x4 |
apigw.medium.x1 |
apigw.medium.x2 |
apigw.medium.x3 |
apigw.large.x1 |
apigw.large.x2 |
apigw.large.x3 |
apigw.large.x4 |
|||
|
Connection type |
Response size (KB) |
HTTPS |
Gzip compression |
QPS reference |
||||||||||
|
Short-lived Connections |
1 |
No |
No |
1,700 |
3,400 |
6,800 |
13,600 |
28,000 |
56,000 |
84,000 |
112,000 |
224,000 |
336,000 |
448,000 |
|
Yes |
No |
500 |
1,000 |
2,000 |
4,000 |
8,700 |
17,400 |
26,100 |
34,800 |
69,600 |
104,400 |
139,200 |
||
|
Long-lived Connections |
1 |
No |
No |
2,200 |
4,400 |
8,800 |
17,600 |
35,000 |
70,000 |
105,000 |
140,000 |
280,000 |
420,000 |
560,000 |
|
Yes |
No |
2,000 |
4,000 |
8,000 |
16,000 |
32,000 |
64,000 |
96,000 |
128,000 |
256,000 |
384,000 |
512,000 |
||
|
Yes |
Yes |
1,700 |
3,400 |
6,800 |
13,600 |
28,000 |
56,000 |
84,000 |
112,000 |
224,000 |
336,000 |
448,000 |
||
|
10 |
No |
No |
1,800 |
3,600 |
7,200 |
14,400 |
30,000 |
60,000 |
90,000 |
120,000 |
240,000 |
360,000 |
480,000 |
|
|
Yes |
No |
1,700 |
3,400 |
6,800 |
13,600 |
28,000 |
56,000 |
84,000 |
112,000 |
224,000 |
336,000 |
448,000 |
||
|
Yes |
Yes |
1,000 |
2,000 |
4,000 |
8,000 |
16,000 |
32,000 |
48,000 |
64,000 |
128,000 |
192,000 |
256,000 |
||
Quota limits
Global quotas
Global quotas apply to all instance specifications. To increase a quota, submit a ticket.
|
Quota item |
Quota |
|
Number of instances per region |
100 |
|
Number of operations per API |
2,000 |
Instance-specific quotas
Quotas scale with the instance specification. If you upgrade and the quota is still insufficient, submit a ticket to request an increase.
|
Dev |
Small |
Medium |
Large |
|
|
Number of published domain names |
100 |
200 |
500 |
1,000 |
|
Number of associated services |
200 |
800 |
2,000 |
4,000 |
|
Number of service nodes |
400 |
1,600 |
4,000 |
8,000 |
|
Total routes (including HTTP API routes, REST API operations, and Ingress routes) |
2,500 |
5,000 |
7,500 |
10,000 |
|
Number of Kubernetes service sources |
3 |
3 |
5 |
5 |
|
Number of installed plugins |
5 |
10 |
20 |
30 |
|
Number of uploaded custom plugins |
10 |
20 |
50 |
80 |
|
Number of consumer authorizations |
500 |
2,000 |
6,000 |
10,000 |