Versions Compared

Version Old Version 1 New Version Current
Changes made by

Kolawole Adebisi-Adeolokun

Kolawole Adebisi-Adeolokun

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel6
outlinefalse
styledefault
typelist
printabletrue

References

Jira Legacy
columns
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-2169
 

...

Issues & Decisions

InterfaceRequirementAdditional InformationSignoff1

Issue

Notes 

Decision

1

Issues & Decisions

...

Requirements

Functional

Review the use case returning all 50k cmHandle

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

AP Csaba Kocsis & kieran mccarthy 

  1. Returning all 50k cmhandles will impact the speed and overall performance. Focus on Read & Write

  2. Review usecases that don’t need to return all 50k cmhandles. kieran mccarthy

2

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

  • CPS optimised locking mechanism on the bug

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-2403

  • Still open pending CPS completion of Hazelcast study -

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-2161

3

DDP Metrics Collection

CPS to investigate how DDP metrics can be collected to investigate client usecase of AP Daniel Hanrahan

Requirements

Functional

Operations

Parallel/Sequential

DMI Delay

Response Size

Performance

Additional Information

Signoff

1

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 to move to → 3min

kieran mccarthy

2

CM-handle ID Search

5 Parallel

  1. No frequency increase expected

  2. Search shall return all 50k searches ?

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

 

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

kieran mccarthy

3

CM-handle search

5 Parallel

  1. No frequency increase expected

  2. Search shall return all 50k searches ?  

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

 

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

No change TBD AP; Peter Turcsanyi kieran mccarthy

4

Synchronous single CM-handle pass-through Read (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

  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. No changes to Delay is expected

Policy executor have different test suit and won’t be impacted by this

kieran mccarthy

5

Synchronous single CM-handle pass-through Write

4 (Parallel operations)

  1. Frequencies will increase (2.5) currently 5 request/second for 80k cells = 12.5 req/sec for 200k cells

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

kieran mccarthy

  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

  5. No volume increase expected

 

6

Batch Read Operation/Legacy 

  1. Frequencies will increase (2.5)

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

  3. Same duration of test, No changes to volume expected

  4. Responses are expected back in 80 sec.

Investigation needed because target is not met at this point

7

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,300  / sec (base/Average load)

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

  3. Daily Average

  4. Base:

  5. Average:

  6. Peak: 

  7. Storm:

  8. Load distribution discussion still pending

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

Use number on FS and * 2.5 as the source of truth

Error Handling

Scenario

Expected Behavior

Notes

Signoff

1

Characteristics 

Parameter

Expectation

Notes

Signoff

1

Robustness

Scenario

Input Load

Performance

Notes

Number of NCMP Instances

Signoff

1

Base Performance & Performance

2

Average Performance & Duration

3

Peak Performance & Duration

4

Number of Instances

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

Out of Scope

  • Datajob which is still in development are out of scope

  • For now Paging is out of scope, open to rescope depending on NCMP spike result

Solution Proposal