Versions Compared

Key

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

...

Issues & Decisions

see

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

Will wait Awaiing 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.


OperationTotal CM-handles registeredConcurrent requests/parallelDMI Delay
Notes
Rest response sizePerformance
Observed Rate
(rate not measured)

Expected duration

NotesSign-Off
1Registration of 100 CM-handles20k Nodes (200 operations)1 (requests are sequential)

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

N/A

  • 11 NEs/second as per Stone Tablet
  • 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

ST

ST 

N/A

11 NEs/second ST

NCMP should be target 22 NEs/Second 

TBD21 May
2De-registration of 100 CM-handles20k Nodes (200 operations)1 (requests are sequential)

No Module delays

Not in the StoneTablet.

N/A

  • 11 NEs/second
CPS
  • NCMP should
be
  • target 22 NEs/Second 
CPS to record & report

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




3CM-handle ID search with Module filter20k Nodes

2.5 parallel (5)

N/A
Combine test3&4 to = 5 (2.5 each)
100byte*20k

TBD will be derived when testing is done in ETH envi

Combine test3&4 to = 5 (2.5 each)TDB
4CM-handle search with Module filter20k Nodes2.5 parallelN/A500bytes*20k per handleTBD will be derived when testing is done in ETH envi
TDB
5Synchronous single CM-handle pass-through read20k Nodes

10

Awaiting input from eth Csaba Kocsis

Read are done in parallel with Writes

5 KB

25 op/sec shall not exceed

TBD

Read are done in parallel with Writes

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

10

Awaiting input from eth Csaba Kocsis 

No response is expected

5kb

13 ops/sec 

TBD
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

...