Read data operation resource for multiple cm-handles
Capabilities
# | Parameter | Expectation | Notes |
|---|---|---|---|
| 1 | Response Time 1 Batch request | <2 seconds (average) |
|
| 2 | Batch-size | 200 cm handles | No hardcoded limit |
| 3 | Response payload size | ~2 KB per cm handles | Performance test for capability should be tested with this average response size |
| 4 | Maximum registered #cm handles | 20,000 | This will effect the internal query time |
| 5 | Supported # DMI PLugins | 10 | This might effect processing times |
| 6 | Test Environment | ||
| 7 | Concurrent request | 12 | 12 clients requests toward 1 NCMP simultaneously |
| 8 | Request Frequency | 100 request/min | Should not affect performance, does not need to be tested |
Test Configurations
# | Environment/Workload | Description |
|---|---|---|
| 1 | Tested on | laptop : |
| 2 | Shell script, postman request and generated txt file with 20,000 cm handle ids | |
| 3 | Number of CPS Instance | 1 |
| 4 | Number Modules per Cm Handle | 10 |
| 5 | Total number of cm handles | 20,000 |
| 6 | Commit ID | |
| 7 | Commit ID link | https://gerrit.onap.org/r/gitweb?p=cps.git;a=commit;h=9830d1aec56da5cec195f6d15c318b58f642c9b7 |
# | Component | Configuration Parameters | Value |
|---|---|---|---|
| 1 | CPS | notifactions:enabled | true |
| 2 | CPS | config.additional.notification.data-updated.filters.dataspaces.enabled-dataspaces | "NON-EXISTING-DATASPACE" |
| 3 | NCMP | modules-sync-watchdog:async-executor:parallelism-level | 10 |
Summary of test results
# | Tool | Response to client topic | Timestamp |
|---|---|---|---|
| 1 | offset explorer | 1st cm handle response | 2023-07-20 14:07:50.456 |
| 2 | offset explorer | last cm handle response | 2023-07-20 14:08:03.672 |
| Total time taken to publish 20,000 cm handle response to client topic | 13 seconds 216 milliseconds (13,216 ms) | ||
| Pace of cm handle response to client topic | 1,514 cm handle response / sec | ||