CPS-2169: NCMP to support 50K CM-handles

References

CPS-2169 - Getting issue details... STATUS

	Issue	Notes	Decision
1	Review the use case returning all 50k cmHandle	Validity of the use case where ALL 50k CMhanlde are expected to be returned everytime ? AP Csaba Kocsis & kieran mccarthy

	Requirement	Additional Information
1	Registration & De-registration (Discovery) With moduleSetTag With AID	Parallel/Sequential ? tbc Batch size of 100 The whole cmhandle should be in ready state @the moment - TBC (should change to rate)
2	CM-handle search	Frequency will increase by 2.5 of current capacity Search shall return all 50k searches ? @NCMP to confirm Searches shall return all 50k searches within 1 minute max
3	CM-handle ID Search	Frequency will increase by 2.5 of current capacity Search shall return all 50k searches ? @NCMP to confirm Searches shall return all 50k searches within 1 minute max
4	Synchronous single CM-handle pass-through write (CUD)	Frequencies will increase (2.5) atm TBC Response time should stay the same as current (delay, size
5	Synchronous single CM-handle pass-through Read	Frequencies will increase (2.5) atm TBC Response time should stay the same as current delay, size
6	Batch Operation/Legacy
7	CM change notification NCMP shall support a CM notification load of 150 million CM change notifications per day with an average of 870 notification NCMP shall support a peak CM change notification load of 7k/s for a duration 5 minutes

	Scenario	Expected Behavior	Notes	Signoff
1

	Parameter	Expectation	Notes	Signoff