/
CPS-2690: DCM Characteristics

CPS-2690: DCM Characteristics

 

References

CPS-2690: DCM Characteristics In Progress

 

Summary

DCM write measurement within // is for arpound100k operation request took about 21minutes before a response was returned, which is not acceptable

 

Issues & Decisions

Issue

Notes 

Decision

Issue

Notes 

Decision

1

How many requests will be done in parallel (especially for 100,000 operations)?

  1. 10 parallel request - Small (1-100)

  2. 1 request - Large (100,000)

Mar 11, 2025 @Csaba Kocsis

  1. 10 parallel request - Small (1-100)

  2. 1 request - Large (100,000)

2

How many cm-handles are involved in a single request ?

  1. the current sample has only 1 cmhandle

  2. Nodes are managed element

Mar 11, 2025 @Csaba Kocsis

test should be done for

  1. 20k different cmhandles

  2. 50k different cmhandles

// to align

3

Are the private properties needed?

currently not included in NCMP, if included, it could adversely impact performance

Mar 11, 2025 @Csaba Kocsis

  1. Private properties. have not been included in dcm within // not needed

  2. AP; @Kolawole Adebisi-Adeolokun to update documentation for removal of private properties

4

 

 

 

Performance Requirement

PS; NCMP only uses alternateid for DCM testing

Operations

Response Size

Expected Performance

Notes

Sign-Off

Operations

Response Size

Expected Performance

Notes

Sign-Off

1

The system must support 100,000 operations per request, with each operation having an average size of 300 bytes

 

 

  1. Write Throughput: NCMP must handle at least 10,000 write data jobs per day.

  2. What is the limit of singleness respond - should be within http timeout?

 

2

The system must also support 100,000 operations spread across multiple handles instead of a single bulk request.