...
| Note |
|---|
Please note this section was added long after the implementation and focuses on characteristic only. |
Characteristics
...
- WIP
It is proposed that reported characters characteristics will be used as a baseline for agreed limitsNCMP when agreed and sign-off.
| Operation | Total CM-handles registered | Concurrent requests/parallel | DMI Delay | Rest response size | Notes | Performance | Observed Rate (rate not measured) | Expected duration | Sign-Off | |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Registration of 100 CM-handles | 20k Nodes | 1 (requests are sequential) | 100 ms to get module references | N/A | 1.6 ops/second | TBD | TDB | ||
| 2 | De-registration of 100 CM-handles | 20k Nodes | 1 (requests are sequential) | N/A | N/A | |||||
| 3 | CM-handle search without filter | 20k Nodes | 5 | N/A | TBD e.g. 10MB | All 20k returned | Within 15 sec | 5 ops/minute | 1 minute / operation | TDB |
| 4 | CM-handle ID search without filter | 20k Nodes | 5 | N/A | TBD e.g. 1MB | All 20k shall be returned | Within 2 sec | 7.1 ops/minute | 42 seconds / operation | TDB |
| 5 | Synchronous single CM-handle pass-through read | 20k Nodes | 20 |
TDB e.g. 5 KB | 25 op/sc | 50 ops/second | TBD | TDB | |||
| 6 | Synchronous single CM-handle |
| response time read | 20k Nodes | 20 |
Daniel Hanrahan will obtain figures
N/A |
within 1 sec | ||||||||||
| 7 | Synchronous single CM-handle pass-through write | 20k Nodes | 20 | N/A | N/A | 13 ops/sec | 13 ops/second | TBD | TDB | |
| 8 | Synchronous single CM-handle response time write | 20k Nodes | 20 | N/A | Within 2 sec |
Note:
- This is for mixed TCs
- Single KPIs will be monitored in NCMP owned pipeline with our performance every day(2 hrs interval) - Performance
- New BATCH KPI - TBD
- Organise a call to walk through the code and TCs with ETH. Want to see the code of the Test Cases. Csaba Szabó to walkthrough TCs with CPS team
- Check Registration & de-reg agree with them
Open Questions
- Concurrent which number are we agreeing to test, 10 according to the input load/ average response time as mentioned in comment
- DMI delay - We need feed back from ETH on this
- Better to have R, W use cases separated as in the FS for both throughput and response time or should we merge this on NCMP
- Check Registration - Refer to Michelle email for the numbers
- Check DE-Registration if that was ever agreed
Synchronous single cm-handle pass-through (read) requests
...