3.3.1 Profile Resource Requirements for 110K MPS SCP Profile Message Sequencing
The following table displays the profile resource requirements for 110K MPS SCP Profile.
Note:
For a vCNE setup update the value of the parameter numIoThreads to "3024" in the custom-values.yaml file.Table 3-5 Resource Requirements
OCNADD Service | 110K MPS SCP Profile | |||
---|---|---|---|---|
Replication Factor = 2 (vCNE) Message Size = 3500 FEED Type = HTTP2/TCP/KAFKA |
vCPU | Total Replica |
Memory Required (Gi) |
Topic Partitions |
Kafka with RF=2 | ||||
ocnaddkafka | 6 | 4 | 164 | - |
MESSAGE_SEQUENCING_TYPE = TRANSACTION, TRANSACTION_MSG_SEQUENCING_EXPIRY_TIMER= 200ms | ||||
ocnaddscpaggregation | 2 | 5 | 24 | SCP=30 |
MESSAGE_SEQUENCING_TYPE = TIME_WINDOW, WINDOW_MSG_SEQUENCING_EXPIRY_TIMER=10ms | ||||
ocnaddscpaggregation | 2 | 5 | 24 | SCP=30 |
MESSAGE_SEQUENCING_TYPE = REQUEST_RESPONSE, REQUEST_RESPONSE_MSG_SEQUENCING_EXPIRY_TIMER=10ms | ||||
ocnaddscpaggregation | 2 | 5 | 16 | SCP=30 |
INGRESS FILTER is ON | ||||
MESSAGE_SEQUENCING_TYPE = TRANSACTION, TRANSACTION_MSG_SEQUENCING_EXPIRY_TIMER= 200ms | ||||
ocnaddscpaggregation | 2 | 6 | 36 | SCP=36 |
MESSAGE_SEQUENCING_TYPE = TIME_WINDOW, WINDOW_MSG_SEQUENCING_EXPIRY_TIMER=10ms | ||||
ocnaddscpaggregation | 2 | 6 | 36 | SCP=36 |
MESSAGE_SEQUENCING_TYPE = REQUEST_RESPONSE, REQUEST_RESPONSE_MSG_SEQUENCING_EXPIRY_TIMER=10ms | ||||
ocnaddscpaggregation | 2 | 6 | 24 | SCP=36 |
HTTP2 FEED (FILTER = OFF) | ||||
ocnaddadapter | 3 | 14 | 4 | MAIN=126 |
SYNTHETIC FEED (TCP CONNECTION MESSAGE and/or MESSAGE SEGEMENTATION = ON) (FILTER=OFF) | ||||
ocnaddadapter | 3 | 10 | 12 | MAIN=60 |
Note:
- The performance run is completed with a 90% success rate of transactions. (Success Transaction = All four transaction messages (RxRequest, TxRequest, RxResponse, and TxResponse) received from SCP).
- The number of instances for SCP aggregation may increase from the defined number in the resource profile based on the message sequencing timer expiry configuration (using the Max timer expiry value) and the Transaction success rate.
- The end-to-end latency may increase based on "Timer Expiry Value + Processing Time + RF2 Processing Time + 3rd party response time (For HTTP2 Feed)".