CPS-2169: NCMP to support 200k Cells (50KCM-handles)

Review the use case returning all 50k cmHandle

Validity of the use case where ALL 50k CMhandles are expected to be returned everytime ?

AP @Csaba Kocsis & @kieran mccarthy 

Sep 30, 2024 

AP CPS to report where they think scalability issues will occur.

Oct 30, 2024 TBC @kieran mccarthy

Proposal to remove hazelcast for NCMP Module sync

The use of Hazelcast during NCMP's CM-handle Module Sync is leading to:

1. High memory usage during CM-handle registration

2. Consistency problem

3. Poor load balancing between NCMP instances for module sync

Proposal to remove hazelcast from NCMP Module Sync requires an LCM State Machine Change. Need stakeholder input.

Proposal:  CPS-2161: Remove Hazelcast from NCMP Module Sync

Oct 30, 2024

• CPS optimised locking mechnism on the bug CPS-2403: CmHandle discovery degradationClosed

• Still open pending CPS completion of Hazalcast study

Registration & De-registration (Discovery) In Batch size of 100 per request.

• With moduleSetTag &

• With alternateID

Parallel

1. How long should it take cmhandle to reach in ready state - 11 Cm Handles/second per NCMP instance.

2. Overall budget; @Peter Turcsanyi
   a. Advise → locked → Ready: ?
   b. Advise → Ready: ?

3. Initial delay ; Currently 2 min. TBC @Peter Turcsanyi

4. System driven load from topology Request ? @Peter Turcsanyi

Nov 19, 2024

CM-handle ID Search

5 Parallel

1. Frequency will increase by 2.5 of current capacity

2. Search shall return all 50k searches ?

3. Searches shall return all 50k searches within 1 minute max TBD

4. Base:

5. Average:

6. Peak:

Aug 28, 2024 

1. 5 parallel request of ID search and search, = combined total of 10 parallel search requests.

Nov 19, 2024

TBD; AP @Peter Turcsanyi

CM-handle search

5 Parallel

1. Frequency will increase by 2.5 of current capacity - CPS-391Spike: Define and Agree NCMP REST Interface - Developer Wiki - Confluence (onap.org)

2. Search shall return all 50k searches ?  

3. Searches shall return all 50k searches within 1 minute max TBD

4. Base:

5. Average:

6. Peak:

Aug 28, 2024 

1. 5 parallel request of ID search and search, Total of 10 parallel search requests.

Nov 19, 2024

No change TBD AP; @Peter Turcsanyi

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

4 parallel Operations

Review; the current FS numbers

1. What will be frequencies for write req. ? AP: TBD

2. Frequencies will increase (2.5); 10 req/sec= 25 req/sec

3. Response time should stay the same as current - NCMP Characteristics

Nov 19, 2024

1. Stick with 10 req/sec= 25 req/sec (Should CPS PoC it?) to measure the current no of req.

2. CPS measure current capacity

3. CPS will engage in Setting the frequency (Based on previous result)

4. Share with stakeholder

5. No changes to Delay is expected

Synchronous single CM-handle pass-through Read

4 (Parallel operations)

1. Frequencies will increase (2.5) atm TBC

2. Response time should stay the same as current NCMP Characteristics (delay, size)

Nov 19, 2024

1. CPS measure current capacity

2. CPS will engage in Setting the frequency (Based on previous result)

3. Share with stakeholder

4. No changes to Delay is expected

Batch Read Operation/Legacy 

1. Frequencies will increase (2.5)

2. Same load 200 per request (Same response size)

3. Same duration of test

4. Responses are expected back in 80 sec.

Nov 19, 2024

TBD AP; @Peter Turcsanyi

CM change Notification Event

1. NCMP shall support a CM notification load of 150 million CM change notifications per day with an average of 870 notification

2. NCMP shall support a peak CM change notification load of 7k/s for a duration 5 minutes

1. 2,175  / sec (base/Average load)

2. 8.75 k/sec (peak load) TBC @kieran mccarthy

3. Base:

4. Average:

5. Peak: 

Nov 19, 2024

Current numbers on FS as of today should be by 2.5 (non-negotiable).

Base Performance & Performance

Average Performance & Duration

Peak Performance & Duration

Number of Instances

TBC - Each NCMP instance takes 11 CM-Handles/second.