INTRODUCTION
Based on the xES provided statistics of agent traffic, Service Gateway performed the performance testing to get the sizing integration with xES.
As the sizing is based on the details of traffics, it may be different with the customer environment. This article can only be used as a reference.
Test Scenarios
Table 1: Regular Agent Network Traffic for testing:
| V1 Agents Type | Package Size | Frequency of polling (API request) | |
|---|---|---|---|
| 1 | XBC | 2.7 MB |
|
| 2 | WSC | 1.7 MB |
|
Table 2: concurrent connection for product request
| API | XBC and WSC agents Size |
|---|---|
| Concurrent connections(agents) | 10000 |
| Concurrent connections(agents) | 20000 |
| Concurrent connections(agents) | 30000 |
Test Results
Table 2-2 Test Results
| Platform | ESXI 6.5 | ESXI 6.5 | ESXI 6.5 | ESXI 6.5 |
|---|---|---|---|---|
| Hardware model | 8vCPU/12G Mem/500G | 8vCPU/12G Mem/500G | 8vCPU/12G Mem/500G | 8vCPU/12G Mem/500G |
| Protocol | HTTPS | HTTPS | HTTPS | HTTPS |
| Running status | running without load | running with load | running with load | running with load |
| Client count | 0 | 10000 | 20000 | 30000 |
| Concurrent connection | 0 | 10000 persistent IOT | 20000 persistent IOT | 30000 persistent IOT |
| TPS | - | 20 API request | 35 API request | 50 API request |
| Avg. CPU Usage | 4.96% | 6.98% | 8.13% | 8.89% |
| Avg. Mem Usage | 27.35% | 33.74% | 43.90% | 58.30% |
| Avg. Disk IO Usage | 0.91% | 1.16% | 1.34% | 1.42% |
| Avg. Network Traffic | - | - | - | - |
TPS: means transaction per second, T(transaction) means API request from a XBC or WSC agent.
Conclusion
One Service Gateway appliance can support at most 30K xES Agents.
By the increase of concurrent connections, SG uses more Mem and CPU, and there is no obvious increase in the usage for the Disk IO, all the resource usage did not exceed 80%.
From the test, the persistent connections mainly cost Mem resource.