Versions Compared

Old Version 158

changes.mady.by.user Kolawole Adebisi-Adeolokun

Saved on

compared with

New Version 159

changes.mady.by.user Kolawole Adebisi-Adeolokun

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

It is proposed that reported characteristics will be used as a baseline for NCMP when agreed and sign-off.


OperationTotal CM-handles registeredConcurrent requests/parallelDMI DelayRest response sizePerformanceObserved Rate
(rate not measured)

Expected duration

Sign-Off
1Registration of 100 CM-handles20k Nodes1 (requests are sequential)

100 ms to get module references
1000 ms to get module resources

N/A


1.6 ops/secondTBDTDB
2De-registration of 100 CM-handles20k Nodes1 (requests are sequential)

N/A

N/A





3CM-handle search without filter20k Nodes5N/ATBD e.g. 10MBWithin 15 sec5 ops/minute1 minute / operationTDB
4CM-handle ID search without filter20k Nodes

5

N/ATBD e.g. 1MBWithin 2 sec7.1 ops/minute42 seconds / operationTDB
5Synchronous single CM-handle pass-through read20k Nodes

20


TDB e.g. 5 KB

25 op/sec

50 ops/secondTBDTDB
6Synchronous single CM-handle response time read20k Nodes

20

N/A


within 1 sec




7Synchronous single CM-handle pass-through write20k Nodes

20

N/A

N/A

13 ops/sec 

13 ops/secondTBDTDB
8Synchronous single CM-handle response time write20k Nodes

20

N/A


Within 2 sec





Note

  1. This is for mixed TCs
  2. Single KPIs will be monitored in NCMP owned pipeline with our performance every day(2 hrs interval) - Performance
  3. New BATCH KPI - TBD
  4. 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
  5. Check Registration & de-reg agree with them // 

Open Questions

  1. 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
  2. DMI delay - We need feed back from ETH on this
  3. 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
  4. Check Registration - Kolawole Adebisi-Adeolokun  Refer to Michelle's email
  5. Check DE-Registration if that was ever agreedRegistration 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)
  1. Functional Specification document.
    1. 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.

                                                       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.

                                                      iii.      AP @Csaba Kocsis Notify Product Engineering (Dagda) about the change.


    1. AP , @Csaba Kocsis  , @Toine Siebelink, @Kolawole Adeolokun: Review the FS and identify if additional information is required. ONGOING

                                                         i.      23rd April: FS reviewed and 2 comments added by Toine.


    1. 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


    1. Can FS to be updated to define single / individual workload. Where can it be tested?  AP @Kieran Mccarthy A, @Csaba Kocsis, @Toine Siebelink


Synchronous single cm-handle pass-through (read) requests

...