Results of module set tag performance tests with 20K CmHandles. (v3.4.7)
It's very likely that the wrong data was recorded for the first test scenario. Realistically the figures are 11 minutes and 1818 CM Handles/minute
Test case | Time to complete request | cm handles processed/minute | |
|---|---|---|---|
| 1 | initial registration with (10 different) module set tags | 2m24s | 8,333 |
| 2 | initial registration without module set tags | 25m | 800 |
| 3 | upgrade module set tags to new one (all same) | 3m45s | 5,333 |
| 4 | upgrade module set tags to an existing one | 1m3s | 19,047 |
Latest test result (v3.5.2-SNAPSHOT)
Test case | Time to complete request | cm handles processed/minute | |
|---|---|---|---|
| 1 | initial registration with (10 different) module set tags | 8m30sec | 2,352 |
| 2 | initial registration without module set tags | 19m | 1052 |
Test Environment
# | Environment/Workload | Description |
|---|---|---|
| 1 | Tested on | laptop : |
| 2 | Number of CPS Instance | 1 |
| 4 | Total number of cm handles | 20,000 |
| 5 | Batch-size | N/A |
| 6 | Response payload size | N/A |
| 7 | Concurrent request | 1 |
| 8 | Number of DMI PLugins | 1 |
| 9 | Commit ID | I0adcac52a7a49e26301758eafc4684152ddfcaf5 |
| 10 | Commit ID link | Scripts for performance test |
| 11 | Postman collection |
...