Versions Compared

Old Version 167

changes.mady.by.user Kolawole Adebisi-Adeolokun

Saved on

compared with

New Version 168

changes.mady.by.user Toine Siebelink

Saved on

Key

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

...


IssuesNotesDecisions
1KPI for De-registration of 100 CM-handlesThis 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

Awaiing Awaiting for ETH feedback AP On Kolawole Adebisi-Adeolokun and Csaba Kocsis

...

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/parallelDMI Delay
Rest response
Response sizePerformance Requirement
(Blue Stone tablet KPI)		NotesSign-Off
1Registration of
100
20,000 CM-handles
20k Nodes (200 operations
(in batches of 100)1 (requests are sequential)

100 ms to get module references

1000

1,000 ms to get module resources

N/A

  • 11
NEs
  • CM-Handles/second as per Stone Tablet E2E Wich include module conversion warm-up
  • NCMP
should target 22 NEs/Second 

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
  • 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.
ST 

Csaba Kocsis Toine Siebelink 

2De-registration of 100 CM-handles
20k Nodes (200 operations)
1 (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
20k Nodes

2.

5 parallel (5)

5 
Run in parallel with #4

N/A
100byte*20k = 
20,000 CM Handles i.e.
100*20.000 = 2MB

TBD will be derived when testing is done in ETH envi Daniel Hanrahan 

Combine test3&4 to = 5 (2.5 each)


TDB
4CM-handle search with Module filter
20k Nodes
2.
5 parallel
5 
Run in parallel with #3		N/A
500bytes*20k per handle = 10
20,000 CM Handles i.e.
500*20.000 = 10MB

TBD will be derived when testing is done in ETH envi Daniel Hanrahan 


TDB
5Synchronous single CM-handle pass-through read
20k Nodes

10
Run in parallel with #6

Awaiting input from eth Csaba Kocsis

5 KB

25

op

(parallel) request/sec

shall not exceed

Read are done in parallel with

Writes10

Write

TDB
6Synchronous single CM-handle pass-through write (CUD)
20k Nodes

10
Run in parallel with #5

Awaiting input from eth Csaba Kocsis 

5kb

5 KB

13

ops/sec 

(parallel) request/sec

No response is expectedTDB

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

...