| Operations | Parallel/Sequential | DMI Delay | Response Size | Performance | Additional Information | Signoff |
---|
1 | Registration & De-registration (Discovery) In Batch size of 100 per request. With moduleSetTag & With alternateID
| Parallel | | | How long should it take cmhandle to reach in ready state - 11 Cm Handles/second per NCMP instance. Base: Average: Peak: Overall budget; a. Advise - locked -→ locked → Ready: b. Advise → Ready:
| | |
2 | CM-handle ID Search | | | | | Frequency will increase by 2.5 of current capacity Search shall return all 50k searches ? Searches shall return all 50k searches within 1 minute max TBD
| |
3 | CM-handle search | | | | | Frequency will increase by 2.5 of current capacity - CPS-391Spike: Define and Agree NCMP REST Interface - Developer Wiki - Confluence (onap.org) Search shall return all 50k searches ? Searches shall return all 50k searches within 1 minute max TBD
| |
4 | Synchronous single CM-handle pass-through write (CUD) | | | | | Review; the current FS numbers What will be frequencies for write req. ? TBD Frequencies will increase (2.5) of current performance of 25 request/sec= 62.5req/sec Response time should stay the same as current - NCMP Characteristics
| |
5 | Synchronous single CM-handle pass-through Read | | | | | Frequencies will increase (2.5) atm TBC Response time should stay the same as current NCMP Characteristics (delay, size)
| |
6 | Batch Read Operation/Legacy | | | | | Frequencies will increase (2.5) Same load 200 per request Same duration of test Responses are expected back in 80 sec.
| |
7 | CM change Notification Event NCMP shall support a CM notification load of 150 million CM change notifications per day with an average of 870 notification NCMP shall support a peak CM change notification load of 7k/s for a duration 5 minutes
| | | | | 2,175 / sec (base/Average load) 8.75 k/sec (peak load) TBC kieran mccarthy
| |