...
| Note |
|---|
Please note this section was added long after the implementation and focuses on characteristic only. |
Issues & Decisions
| Issues | Notes | Decisions | |
|---|---|---|---|
| 1 | 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 the Registration | |
| 2 | DMI delay | Could we get some feedback on DMI-delays for other use cases as not mentioned in FS document | |
| 3 | New BATCH KPI | TBD |
Characteristics - WIP
It is proposed that reported characteristics will be used as a baseline for NCMP when agreed and sign-off.
| Operation | Total CM-handles registered | Concurrent requests/parallel | DMI Delay | Rest response size | 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 ID search without filter | 20k Nodes | 5 | N/A | TBD e.g. 1MB | Within 2 sec | 7.1 ops/minute | 42 seconds / operation | TDB |
| 4 | CM-handle search without filter | 20k Nodes | 5 | N/A | TBD e.g. 10MB | Within 15 sec | 5 ops/minute | 1 minute / operation | TDB |
| 5 | Synchronous single CM-handle pass-through read | 20k Nodes | 10 | N/A | TDB e.g. 5 KB | 25 op/sec | 50 ops/second | TBD | TDB |
| 6 | Synchronous single CM-handle response time read | 20k Nodes | 10 | N/A | within 1 sec | ||||
| 7 | Synchronous single CM-handle pass-through write (CUD) | 20k Nodes | 10 | N/A | N/A | 13 ops/sec | 13 ops/second | TBD | TDB |
| 8 | Synchronous single CM-handle response time write (CUD) | 20k Nodes | 10 | N/A | Within 2 sec |
...
Notes
- 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 //. Want to see the code of the Test Cases. Csaba Szabó to walkthrough TCs with CPS team
- Check Registration & de-reg agree with //
Open Questions
- Concurrent which number are we agreeing to test, 10 parallel op. according to the input load, the average response time as mentioned in comment is 20 parallel op
- 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 - Kolawole Adebisi-Adeolokun Refer to Michelle's email
- Check DE-Registration if this was ever agreed
Ongoing Discussion
- Share Test cases per KPI with CPS. AP @Csaba Szabó X to walkthrough TCs with Toine & Daniel(CPS)
- Functional Specification document.
- Confluence: Configuration Handling Functional Specification.
i. Current content shows mixed testcases, all TCs happening in parallel. AP @Csaba Kocsis Clarify what is being run in parallel and update table accordingly. - Waiting for feedback
ii. AP @Csaba Kocsis update UseCase_0005_IdSearch_NoFilter & UseCase_0008_Search_NoFilter to merge the Input Load column to show total of 5 parallel requests. - Waiting for feedback
iii. AP @Csaba Kocsis Notify Product Engineering (Dagda) about the change. - Waiting for feedback
- AP , @Csaba Kocsis , @Toine Siebelink, @Kolawole Adeolokun: Review the FS and identify if additional information is required. ONGOING
...
- Question about FS and Stability test strategy – what is expected to be supported in parallel or what is expected to be tested in series? How is that decided? AP Michelle & @Csaba Kocsis - Waiting for feedback
- Can FS to be updated to define single / individual workload. Where can it be tested? AP @Kieran Mccarthy A, @Csaba Kocsis, @Toine Siebelink - Waiting for feedback
Synchronous single cm-handle pass-through (read) requests
...