...
Follow principles/patterns of RESTCONF RFC-8040 https://datatracker.ietf.org/doc/html/rfc8040
Follow principles/patterns of yang-patch RFC-8072 https://datatracker.ietf.org/doc/html/rfc8040
Follow principles/patterns of RESTCONF NMDA RFC-8527 https://datatracker.ietf.org/doc/html/rfc8527
Requirements
| Note |
|---|
Please note this section was added long after the implementation and focuses on characteristic only. |
Issues & Decisions
| Issues | Notes | Decisions | |
|---|---|---|---|
| 1 | KPI for De-registration of 100 CM-handles | This was mentioned. Was this ever agreed, is this a valid use case that needs to be covered together with the Registration ? | Not priority for now, but acceptable if we match the registration req. |
| 2 | DMI delay | Could we get some feedback on DMI-delays for other use cases as not mentioned in FS document |
Awaiting for ETH feedback AP On Kolawole Adebisi-Adeolokun and Csaba Kocsis |
Characteristics - WIP
It is proposed that reported characteristics will be used as a baseline for NCMP when agreed and sign-off.
Provided | |||
| 3 | Number of instances In some cases, ETH have used 2 instances, can we verify the number of instances for each use case. Some of the req were defined per instance and resources used : Identify which of these ? | Agreed to; CPS use 1 instance currently, but should focus on aligning performance with 2 instances for all use case | |
| 4 | Input Load Distribution the CM-handle search and ID search | Currently has 5 parallel request between them distributed at 2.5 each. This fractional distribution isn't feasible for parallel processing; the load should be allocated as whole numbers. Load needs to be distributed at. Would it be acceptable to adjust this distribution to either 2 or 3 parallel requests each (and vice versa ) without any negative repercussions? Agreed to do 6 parallel request combined total and divide the load to 3 parallel request each | |
| 5 | Regarding CM-handle search and ID search | FS only identified Module performance, are there any testing done towards a combined search of properties and modules in a single query Confirmed no other testing was previously done on this..... CPS have the capabilities to do mixed testing. ETH tbc on if they want to consider this ( Csaba Kocsis ) |
Requirements
| Note |
|---|
Please note this section was added long after the implementation and focuses on characteristic and enhancements after this study only. |
Characteristics
It is proposed that reported characteristics will be used as a baseline for NCMP when agreed and sign-off.
| Operation |
|---|
| Concurrent requests/parallel | DMI Delay |
|---|
| Response size | Performance Requirement (Blue Stone tablet KPI) | Notes | Sign-Off |
|---|---|---|---|
| 1 | Registration of |
| 20,000 CM-handles |
| (in batches of 100) | 1 (requests are sequential) | 100 ms to get module references |
1,000 ms to get module resources | N/A |
|
|
Currently without Modulesettag, when // start using Modulesettag, we'll need to revisit these numbers.
- Currently as per FS -
- module references - 20k
- get module resources -1000 unique module ref.
- 5 different types of Nodes
ST
|
| |
| 2 | De-registration of 100 CM-handles |
| 1 (requests are sequential) | No Module delays | N/A |
| De-registration is currently not mentioned in Stone Tablet KPI or FS, however we have agreed to match the performance of registration for now as de-reg is also not a priority at this point |
in time | |||||||
| 3 | CM-handle ID search with Module filter | 3 | N/A | 20,000 CM Handles i.e. 100*20.000 = 2MB | As provided byCsaba Kocsis 0.625 seconds/Operation | FS stated 5 parallel request for both ID search and search. CPS to run with 3 parallel each for both ID search and Search meaning a combine total of 6 parallel request | |
| 4 | CM-handle |
| search with Module filter |
| 3 Run in parallel with #3 | N/A |
TBD will be derived when testing is done in ETH envi
| 20,000 CM Handles i.e. 500*20.000 = 10MB | As provided by Csaba Kocsis 13 seconds/Operation | FS stated 5 parallel request for both ID search and search. CPS to test with 3 parallel each for both ID search and Search meaning a combine total of 6 parallel request | |
| 5 | Synchronous single CM-handle pass-through read |
10
10 | 300 ms |
5 KB | 25 |
(parallel) request/sec |
Read are done in parallel with |
Write |
| 6 | Synchronous single CM-handle pass-through write (CUD) |
10
10 | 670 ms |
5 KB | 13 |
(parallel) request/sec | No response is expected |
| 7 | Batch/Bulk Read | 1 read request with 200 cmHandles per second | 150 cmhandles/sec | The batch data operation is asynchronous. NCMP returns the response on the ncmp-async-m2m kafka topic. |
Notes
- This is for mixed TCs
- Single KPIs will be monitored in NCMP owned pipeline with our performance every day(2 hrs interval) - Performance
...