Versions Compared

Old Version 154

changes.mady.by.user Daniel Hanrahan

Saved on

compared with

New Version Current

changes.mady.by.user Kolawole Adebisi-Adeolokun

Saved on

Key

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

...

Note

Please note this section was added long after the implementation and focusses focuses on characteristic only.

Characteristics

Reported characteristics for NCMP version 3.4.1

It is proposed that reported characters will be used as a baseline for agreed limits.

Issues & Decisions


IssuesNotesDecisions
1KPI for De-registration
OperationConcurrent requestsDMI DelayObserved RateExpectationSign-OffRegistration
of 100 CM-handles
1 (requests are sequential)

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

1.6 ops/secondTBDTDBCM-handle search

5

N/A5 ops/minuteTBDTDBCM-handle ID search

5

N/A7.1 ops/minuteTBDTDBSynchronous single CM-handle pass-through read

20

Daniel Hanrahan will obtain figures

50 ops/secondTBDTDBSynchronous single CM-handle pass-through write

20

Daniel Hanrahan will obtain figures

13 ops/secondTBDTDB

...

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 for de-reg  
kieran mccarthy Kolawole Adebisi-Adeolokun 

2DMI delayCould 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.


OperationConcurrent requests/parallelDMI DelayResponse sizePerformance Requirement
(Blue Stone tablet KPI)		NotesSign-Off
1Registration 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

  • 11 CM-Handles/second as per Stone Tablet E2E Wich include module conversion warm-up
  • NCMP Budget: 22 Cm Handles/second 
  1. Batch Size: 100 (per request)
    Not using Module Set Tags
  2. Time measured start of first rest-call until all cm handle states READY
  3. 1,000 unique module references.
  4. Five different types of Nodes. So 5 requests for Module Resources. Avg 200 modules each.

Csaba Kocsis Toine Siebelink 

2De-registration of 100 CM-handles1 (requests are sequential)

No Module delays

N/A

  • 11 NEs/second
  • NCMP should target 22 NEs/Second 

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




 

Csaba Kocsis 

Toine Siebelink Kolawole Adebisi-Adeolokun 

3CM-handle ID search with Module filter

2.5 
Run in parallel with #4

N/A20,000 CM Handles i.e.
100*20.000 = 2MB

As provided byCsaba Kocsis 0.625 seconds/Operation


 Kolawole Adebisi-Adeolokun 

4CM-handle search with Module filter2.5 
Run in parallel with #3		N/A20,000 CM Handles i.e.
500*20.000 = 10MB

As provided by Csaba Kocsis 13 seconds/Operation


Kolawole Adebisi-Adeolokun

5Synchronous single CM-handle pass-through read

10
Run in parallel with #6

300 ms Csaba Kocsis

5 KB

25 (parallel) request/sec

Read are done in parallel with Write

Kolawole Adebisi-Adeolokun 

6Synchronous single CM-handle pass-through write (CUD)

10
Run in parallel with #5

670 msCsaba Kocsis 

5 KB

13 (parallel) request/sec

No response is expected

 Kolawole Adebisi-Adeolokun 

Notes

  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. As confirmed, test was carried out on 2 instances in ETH env. CPS validated 2 replica instances have show considerably better test performance - CPS-2038


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

...