3 Resource Requirement

This chapter provides information about the resource requirements to install and run Oracle Communications Network Analytics Data Director (OCNADD) with the desired Message Per Second (MPS) profiles.

Resource Requirements for CNE Environment

Resource requirements for Baremetal (with NVMe):

Table 3-1 Bare Metal Environment

Type of Server	X9 Server and NVME
Master node	3
Worker node	19
Storage Class	Standard

Resource Requirements for OCI Environment

• OCI block volume is attached to the PVC with auto-tune based performance from balanced to high performance. To change block volume to auto-tune based performance (Balance to High Performance), see Changing the Performance of a Volume.
• All tests are performed with the default round-robin based ordering.
• Resource requirements may vary after enabling key or custom based ordering and running traffic with actual NFs.

Table 3-2 OKE Worker Nodes

Type of Server	OCI Hardware
Worker nodes	6
Instance Shape	VM.Standard.E4.Flex
OCPUs in worker node	50 (CPU: 100)
Memory in worker node	194 GB

3.1 Profile Resource Requirements

This section provides information about the profile resource requirements to install and run Oracle Communications Network Analytics Data Director (OCNADD) with the desired Message Per Second (MPS) profiles.

Note:

It is recommended to have the following configurations for Baremetal setup to achieve the required throughput:

• Jumbo frames should be enabled.
• Ring buffer size should be increased to avoid packet drop at interfaces.
• FluentD pods should not be in "CrashLoopBackOff" state due to Out of Memory error. For more information see "High Latency in adapter feeds due to high disk latency" section in Oracle Communications Network Analytics Data Director Troubleshooting Guide.

• Resource Profile for Database
• Resource Profile for OCNADD OAM Services
• Resource Profile for OCNADD Worker Group Services
• Resource Profile for OCI Environment

3.1.1 Resource Profile for Database

This section provides information about the database profile resource requirements to install and run Oracle Communications Network Analytics Data Director (OCNADD) with the desired Message Per Second (MPS) profiles.

Table 3-3 Resource Requirement

cnDBTier Pods	Min vCPU	Max vCPU	Min Memory	Max Memory	Total Replica
SQL (ndbmysqld) Kubernetes Resource Type: StatefulSet	1	1	1Gi	1Gi	0
SQL (ndbappmysqld) Kubernetes Resource Type: Statefulset	1	1	1Gi	1Gi	2
MGMT (ndbmgmd) Kubernetes Resource Type: StatefulSet	1	1	1Gi	1Gi	2
Database (ndbmtd) Kubernetes Resource Type: StatefulSet	1	1	4Gi	4Gi	2
Backup Manager Service (db-backup-manager-svc) Kubernetes Resource Type: Deployment	0.1	0.1	128Mi	128Mi	1
Monitor Service (db-monitor-svc) Kubernetes Resource Type: Deployment	0.2	0.2	500Mi	500Mi	1
EXTENDED STORAGE is ENABLED in CORRELATION Feed(Per Correlation Feed) Rate Supported in current release: 1K MPS rate with 24 hours retention Update "global.ndb.datamemory=96G" in custom-value.yaml of cndbTier PVC of ndbmtd= 150GB
Database (ndbmtd) Kubernetes Resource Type: StatefulSet	8	8	128Gi	128Gi	4

Note:

Configure "datamemory: 1G" under "ndbmtd" section while deploying the CnDbTier for OCNADD. For more details on cnDBTier resource profile, see "cnDBTier Small Profile" section in cnDBTier Resource Models Guide.

3.1.2 Resource Profile for OCNADD OAM Services

The following profile is used for management group services in all the performance scenarios.

Table 3-4 Resource Requirement

Service Name	vCPU	Memory Required (Gi)	Total Replica	Description
ocnaddconfiguration	1	1	1	-
ocnaddalarm	1	1	1	-
ocnaddadmin	1	1	1	-
ocnaddhealthmonitoring	1	1	1	-
ocnaddgui	1	1	1	-
ocnadduirouter	1	1	1	-
ocnaddexport	0.5	1	1	Resource requirement will increase when export is configured. For more details, see Correlated 30K MPS Kafka Feed.
ocnaddredundancyagent	1	1	1	Required only when Georedundancy is enabled for OCNADD.

3.1.3 Resource Profile for OCNADD Worker Group Services

The following profile shall be used for worker group services. The resource profile for worker group services will vary based on the scenario to be executed.

Note:

To support the increased throughput, the number of topic partitions should be increased. For more details on this, see "Adding Partitions to an Existing Topic" in the Oracle Communications Network Analytics Data Director User Guide.

3.1.3.1 vCNE Cluster Environment

This section gives the details of the LBVM vCNE Cluster Environment.

• Hardware Type: X9-2 Server
• Disk Type: NVMe
• Master node: 3
• Worker node: 44
• LoadBalancer node: LBVM

3.1.3.1.1 Egress 360K MPS Synthetic (TCP) Feed

Note:

DD services and SCP NF services are deployed with anti-affinity enabled at the node level in same cluster.

• Replication Factor: 1
• Message Size: 3500
• Feed Type: TCP
• FILTER: OFF

360K MPS SCP Profile(Ingress to DD)

Table 3-5 360K MPS SCP Profile(Ingress to DD)

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
kraft-controller	1	2	3	-
ocnaddkafka (kafkaBroker)	5	48	11	-
ocnaddscpaggregation	2	4	13	SCP =78 (Each instance 6 partition)
ocnaddadapter(TCP) (consumeradapter)	3	6	20	MAIN=120 (Each instance 6 partition)

Note:

• Additional memory is required for the SCP aggregation service if the Metadata Enrichment feature is enabled and the values of the properties "METADATA_MAP_CACHE_EXPIRY_TIME_MS" and "METADATA_MAP_CACHE_SCHEDULER_TIME_MS" are increased to higher values.
• The end-to-end latency may increase based on "METADATA_MAP_CACHE_EXPIRY_TIME_MS" and "METADATA_MAP_CACHE_SCHEDULER_TIME_MS" is increased to a higher value.
• More instances of the Kafka broker might be required when running with RF=2, depending on setup performance, and end-to-end latency might increase if disk I/O is slow.
• For DISK I/O, see Disk Throughput Requirements.
• For Kafka PVC-Storage, see Kafka PVC Storage Requirements.

3.1.3.1.2 Egress 450K MPS Synthetic (TCP) or HTTP2 Feed

vCNE Cluster Environment

Note:

DD services and SCP NF services are deployed with anti-affinity enabled at the node level in same cluster.

• Replication Factor: 1
• Message Size: 3500
• Feed Type: TCP, HTTP2
• FILTER: OFF

360K MPS SCP Profile(Ingress to DD)

Table 3-6 360K MPS SCP Profile(Ingress to DD)

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
kraft-controller	1	2	3	-
ocnaddkafka (kafkaBroker)	5	96	16	-
ocnaddscpaggregation	2	4	13	SCP =78 (Each instance 6 partition)
ocnaddadapter(TCP) (consumeradapter)	3	6	20	MAIN=120 (Each instance 6 partition)
ocnaddadapter(TCP) (consumeradapter, 360K MPS ingress and 36K MPS egress with Filter)	3	10	7	No partition change as MAIN topic already has 120 partition.
ocnaddadapter(TCP) (consumeradapter, 360K MPS ingress and 36K MPS egress with Filter)	3	10	7	No partition change as MAIN topic already has 120 partition.
ocnaddadapter(HTTP2) (consumeradapter, 360K MPS ingress and 18K MPS egress with Filter)	3	30	5	No partition change as MAIN topic already has 120 partition.

Note:

• Additional memory and/or replica is required for SCP aggregation service if Metadata cache feature is enabled and value of properties "METADATA_MAP_CACHE_EXPIRY_TIME_MS" and "METADATA_MAP_CACHE_SCHEDULER_TIME_MS" is increased to a higher value.
• The end-to-end latency may increase based on: "Timer Expiry Value + Processing Time + RF2/RF1 Processing Time + third-party Response Time (for HTTP2 feed)".
• More instances of the Kafka broker might be required when running with RF=2, depending on setup performance, and end-to-end latency might increase if disk I/O is slow.
• For DISK I/O, see Disk Throughput Requirements.
• For Kafka PVC-Storage, see Kafka PVC Storage Requirements.

3.1.3.2 Bare Metal Cluster Environment

This section gives the details of the Bare Metal Cluster Environment.

3.1.3.2.1 CNLB

This section gives the details of the CNLB Bare Metal Cluster Environment.

• Hardware Type: X9-2 Server
• Disk Type: NVMe
• Master node: 3
• Worker node: 19
• LoadBalancer node: CNLB

3.1.3.2.1.1 Egress 360K MPS Synthetic (TCP) Feed

Note:

There are two separate clusters: one dedicated to OCNADD services, and another shared by SCP NF services and third-party application services.

• Replication Factor: 1
• Message Size: 3500
• Feed Type: TCP
• FILTER: OFF

360K MPS SCP Profile(Ingress to DD)

Table 3-7 360K MPS SCP Profile(Ingress to DD)

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
kraft-controller	1	2	3	-
ocnaddkafka (kafkaBroker)	5	48	11	-
ocnaddscpaggregation	2	4	13	SCP =78 (Each instance 6 partition)
ocnaddadapter(TCP) (consumeradapter)	3	6	20	MAIN=120 (Each instance 6 partition)

Note:

• Additional memory is required for the SCP aggregation service if the Metadata Enrichment feature is enabled and the values of the properties "METADATA_MAP_CACHE_EXPIRY_TIME_MS" and "METADATA_MAP_CACHE_SCHEDULER_TIME_MS" are set to higher values.
• End-to-end latency may increase based on "Timer Expiry Value + Processing Time+ RF2/RF1 Processing Time".
• More Kafka broker instances might be required when running with RF=2, depending on the system's performance. End-to-end latency may also increase if disk I/O is slow.
• For DISK I/O, see Disk Throughput Requirements.
• For Kafka PVC-Storage, see Kafka PVC Storage Requirements.

3.1.3.2.1.2 Egress 450K MPS Synthetic (TCP) or HTTP2 Feed

Bare Metal Cluster Environment

Note:

There are two separate clusters: one dedicated to OCNADD services, and another shared by SCP NF services and third-party application services.

• Replication Factor: 1
• Message Size: 3500
• Feed Type: TCP or HTTP2
• FILTER: OFF

360K MPS SCP Profile(Ingress to DD)

Table 3-8 360K MPS SCP Profile(Ingress to DD)

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
kraft-controller	1	2	3	-
ocnaddkafka (kafkaBroker)	5	96	16	-
ocnaddscpaggregation	2	4	13	SCP =78 (Each instance 6 partition)
ocnaddadapter(TCP) (consumeradapter)	3	6	20	MAIN=120 (Each instance 6 partition)
ocnaddadapter(TCP) (consumeradapter, 360K MPS ingress and 36K MPS egress with Filter)	3	10	7	No partition change as MAIN topic already has 120 partition.
ocnaddadapter(TCP) (consumeradapter, 360K MPS ingress and 36K MPS egress with Filter)	3	10	7	No partition change as MAIN topic already has 120 partition.
ocnaddadapter(HTTP2) (consumeradapter, 360K MPS ingress and 18K MPS egress with Filter)	3	28	5	No partition change as MAIN topic already has 120 partition.

Note:

• Additional memory and/or replica is required for SCP aggregation service if Metadata cache feature is enabled and value of properties. "METADATA_MAP_CACHE_EXPIRY_TIME_MS" and "METADATA_MAP_CACHE_SCHEDULER_TIME_MS" is increased to a higher value.
• The end-to-end latency may increase based on: "Timer Expiry Value + Processing Time + RF2/RF1 Processing Time + third-party Response Time (for HTTP2 Feed)".
• More instances of the Kafka broker might be required when running with RF=2, depending on setup performance, and end-to-end latency might increase if disk I/O is slow.
• For DISK I/O, see Disk Throughput Requirements.
• For Kafka PVC-Storage, see Kafka PVC Storage Requirements.

3.1.3.2.1.3 Aggregated 270K MPS TCP or HTTP2 Feed

When Weighted Load Balancing is ON/OFF and Filter is OFF

• Replication Factor: 1
• Message Size: 3500
• Feed Type: HTTP2 or TCP (single feed at a time either HTTP2 or TCP will be present)
• FILTER: OFF
• Message Sequencing/Filter/Metadata: OFF

15K NRF Profile

Table 3-9 15K NRF Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
kraft-controller	1	2	3	-
ocnaddkafka	2	24	3	-
ocnaddnrfaggregation	2	4	1	NRF=6
ocnaddadapter(HTTP2)	3	3	2	MAIN=18
ocnaddadapter(TCP)	3	3	1	MAIN=18

9K BSF Profile

Table 3-10 9K BSF Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
kraft-controller	1	2	3	-
ocnaddkafka	2	24	3	-
ocnaddbsfaggregation	2	4	1	BSF=6
ocnaddadapter(HTTP2)	3	3	1	MAIN=18
ocnaddadapter(TCP)	3	3	1	MAIN=18

58K PCF Profile

Table 3-11 58K PCF Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
kraft-controller	1	2	3	-
ocnaddkafka	5	24	3	-
ocnaddpcgaggregation	2	4	2	PCF=12
ocnaddadapter(HTTP2)	3	8	4	MAIN=36
ocnaddadapter(TCP)	3	4	3	MAIN=36

128K SCP Profile

Table 3-12 128K SCP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
kraft-controller	1	2	3	-
ocnaddkafka	6	48	4	-
ocnaddscpaggregation	2	4	7	SCP=30
ocnaddadapter(HTTP2)	3	16	10	MAIN=90
ocnaddadapter(TCP)	3	6	6	MAIN=90

60K SEPP Profile

Table 3-13 60K SEPP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
kraft-controller	1	2	3	-
ocnaddkafka	5	24	3	-
ocnaddseppaggregation	2	4	2	SEPP=12
ocnaddadapter(HTTP2)	3	8	4	MAIN=36
ocnaddadapter(TCP)	3	4	3	MAIN=36

270K Aggregated Profile (SCP:128K, NRF:15K, SEPP:60K, PCF=58K, BSF: 9k)

Table 3-14 270K Aggregated Profile (SCP:128K, NRF:15K, SEPP:60K, PCF=58K, BSF: 9k)

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
kraft-controller	1	2	3	-
ocnaddkafka	4	48	11	-
ocnaddscpaggregation	2	4	5	SCP=30 (Each Instance 6 partition)
ocnaddpcgaggregation	2	4	3	PCF=18 (Each Instance 6 partition)
ocnaddbsfaggregation	2	4	1	BSF=6 (Each Instance 6 partition)
ocnaddnrfaggregation	2	4	1	NRF=6 (Each Instance 6 partition)
ocnaddseppaggregation	2	4	3	SEPP=18 (Each Instance 6 partition)
ocnaddadapter(HTTP2)	3	24	23	MAIN=207 (Each Instance 9 partition)
ocnaddadapter(TCP)	3	6	15	MAIN=90 (Each Instance 6 partition)

270K SCP Profile

Table 3-15 270K SCP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
kraft-controller	1	2	3	-
ocnaddkafka	4	48	11	-
ocnaddscpaggregation	2	4	10	SCP=60 (Each Instance 6 partition)
ocnaddadapter(HTTP2)	3	24	23	MAIN=207 (Each Instance 9 partition)
ocnaddadapter(TCP)	3	6	15	MAIN=90 (Each Instance 6 partition)

3.1.3.2.1.4 Aggregated 270K MPS Kafka Feed

When Weighted Load Balancing is ON/OFF and Filter is OFF

• Replication Factor: 1
• Message Size: 3500
• Feed Type: Kafka
• FILTER: OFF
• Message Sequencing/Filter/Metadata: OFF

15K NRF Profile

Table 3-16 15K NRF Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
kraft-controller	1	2	3	-
ocnaddkafka	2	24	3	-
ocnaddnrfaggregation	2	4	1	NRF=6

9K BSF Profile

Table 3-17 9K BSF Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
kraft-controller	1	2	3	-
ocnaddkafka	2	24	3	-
ocnaddbsfaggregation	2	4	1	BSF=6

58K PCF Profile

Table 3-18 58K PCF Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
kraft-controller	1	2	3	-
ocnaddkafka	5	24	3	-
ocnaddpcgaggregation	2	4	2	PCF=12

128K SCP Profile

Table 3-19 128K SCP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
kraft-controller	1	2	3	-
ocnaddkafka	6	48	4	-
ocnaddscpaggregation	2	4	7	SCP=42

60K SEPP Profile

Table 3-20 60K SEPP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
kraft-controller	1	2	3	-
ocnaddkafka	5	24	3	-
ocnaddseppaggregation	2	4	2	SEPP=12

270K Aggregated Profile (SCP:128K NRF:15K SEPP:60K, PCF=58K, BSF=9K))

Table 3-21 270K Aggregated Profile (SCP:128K NRF:15K SEPP:60K, PCF=58K, BSF=9K))

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
kraft-controller	1	2	3	-
ocnaddkafka	4	48	11	-
ocnaddscpaggregation	2	4	5	SCP=30 (Each Instance 6 partition)
ocnaddpcgaggregation	2	4	3	PCF=18 (Each Instance 6 partition)
ocnaddbsfaggregation	2	4	1	BSF=6 (Each Instance 6 partition)
ocnaddnrfaggregation	2	4	1	NRF=6 (Each Instance 6 partition)
ocnaddseppaggregation	2	4	3	SEPP=18 (Each Instance 6 partition)

270K SCP Profile

Table 3-22 270K SCP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
kraft-controller	1	2	3	-
ocnaddkafka	4	48	11	-
ocnaddscpaggregation	2	4	10	SCP=60 (Each Instance 6 partition)

Note:

Number of partition in MAIN topic will be decided based on third-party Kafka consumer.

3.1.3.2.2 LBVM

This section gives the details of the LBVM Bare Metal Cluster Environment.

• Hardware Type: X9-2 Server
• Disk Type: NVMe
• Master node: 3
• Worker node: 19
• LoadBalancer node: LBVM

3.1.3.2.2.1 Aggregated 135K MPS HTTP2 Feed

When Weighted Load Balancing is ON/OFF and Filter is OFF

• Replication Factor: 1
• Message Size: 3500
• Feed Type: HTTP2
• FILTER: OFF
• WLB: WLB is ON/OFF

15K NRF Profile

Table 3-23 15K NRF Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
zookeeper	1	1	3	-
kafkaBroker	2	24	3	-
kafkaBroker (with replicated feed)	2	24	3	-
ocnaddnrfaggregation	2	2	1	NRF=6 (Each Instance 6 partitions)
consumeradapter (HTTP2 feed)	3	3	2	MAIN=18

90K SCP Profile

Table 3-24 90K SCP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
zookeeper	1	1	3	-
kafkaBroker	6	48	4	-
kafkaBroker (with replicated feed)	7	48	4	-
ocnaddscpaggregation	2	4	5	SCP=30 (Each Instance 6 partitions)
consumeradapter (HTTP2 feed)	3	16	10	MAIN=90

30K SEPP Profile

Table 3-25 30K SEPP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
zookeeper	1	1	3	-
kafkaBroker	5	18	3	-
kafkaBroker (with replicated feed)	6	24	3	-
ocnaddseppaggregation	2	4	2	SEPP=12 (Each Instance 6 partitions)
consumeradapter (HTTP2 feed)	3	8	4	MAIN=36

135K Profile (SCP: 90K, NRF: 15K, SEPP: 30K)

Table 3-26 135K Profile (SCP: 90K, NRF: 15K, SEPP: 30K)

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
zookeeper	1	1	3	-
kafkaBroker	6.5	48	6	-
kafkaBroker (with replicated feed)	7.5	96	6	-
ocnaddscpaggregation	2	4	5	SCP=30 (Each Instance 6 partitions)
ocnaddnrfaggregation	2	2	1	NRF=6 (Each Instance 6 partitions)
ocnaddseppaggregation	2	4	2	SEPP=12 (Each Instance 6 partitions)
consumeradapter (HTTP2 feed)	3	24	15	MAIN=135 (Each instance 9 partitions)

135K SCP Profile

Table 3-27 135K SCP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
zookeeper	1	1	3	-
kafkaBroker	6.5	48	6	-
kafkaBroker (with replicated feed)	7.5	96	6	-
ocnaddscpaggregation	2	4	8	SCP=48 (Each Instance 6 partitions)
consumeradapter (HTTP2 feed)	3	24	15	MAIN=135 (Each instance 9-5 partitions)

When Weighted Load Balancing is ON/OFF and Filter is ON

• Replication Factor: 1
• Message Size: 3500
• Feed Type: HTTP2
• FILTER: ON
• WLB: WLB is ON/OFF

15K NRF Profile

Table 3-28 15K NRF Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
ocnaddnrfaggregation (Ingress Filter is ON)	2	2	2	NRF=12 (Each Instance 6 partitions)
consumeradapter (HTTP2 feed with Egress Filter ON)	3	3	3	MAIN=27 (Each instance 9 partitions)

90K SCP Profile

Table 3-29 90K SCP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
ocnaddscpaggregation (Ingress Filter is ON)	2	4	6	SCP=36 (Each Instance 6 partitions)
consumeradapter (HTTP2 feed with Egress Filter ON)	3	3	11	MAIN=99 (Each instance 9 partitions)

30K SEPP Profile

Table 3-30 30K SEPP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
ocnaddseppaggregation (Ingress Filter is ON)	2	2	3	SEPP=18 (Each Instance 6 partitions)
consumeradapter (HTTP2 feed with Egress Filter ON)	3	3	5	MAIN=45 (Each instance 9 partitions)

135K Profile (SCP: 90K, NRF: 15K, SEPP: 30K)

Table 3-31 135K Profile (SCP: 90K, NRF: 15K, SEPP: 30K)

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
ocnaddscpaggregation (Ingress Filter is ON)	2	4	6	SCP=36 (Each Instance 6 partitions)
ocnaddnrfaggregation (Ingress Filter is ON)	2	2	2	NRF=12 (Each Instance 6 partitions)
ocnaddseppaggregation (Ingress Filter is ON)	2	4	3	SEPP=18 (Each Instance 6 partitions)
consumeradapter (HTTP2 feed with Egress Filter ON)	3	24	16	MAIN=144 (Each instance 9 partitions)

135K SCP Profile

Table 3-32 135K SCP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
ocnaddscpaggregation (Ingress Filter is ON)	2	4	9	SCP=54 (Each Instance 6 partitions)
consumeradapter (HTTP2 feed with Egress Filter ON)	3	24	16	MAIN=144 (Each instance 9 partitions)

Note:

• When advanced features such as Ingress filtering, Egress filtering, and Weighted load balancing are enabled simultaneously, the resource requirement for "consumeradapter" service may vary at higher throughput.
• Filter is not tested with replicated feed enabled due to disk I/O limitation.
• Resource requirement may vary when Filter is ON based on % data allowed after filtering and number of filter conditions with configured values.
• Five or Six instances of Kafka brokers might be required when running RF=2, based on the setup performance. The end-to-end latency might increase when DISK I/O is slow.
• For DISK I/O, see Disk Throughput Requirements.
• For Kafka PVC-Storage, see Kafka PVC Storage Requirements.

3.1.3.2.2.2 SCP 270K MPS HTTP2 Feed

When Weighted Load Balancing is ON/OFF and Filter is OFF

• Replication Factor: 1
• Message Size : 3500
• FEED Type: HTTP2
• FILTER: OFF
• WLB: WLB is ON/OFF

Table 3-33 270K MPS HTTP2 FEED

Services	vCPU	Memory Required (Gi)	Total Replica	Topic Partition
zookeeper	1	1	3	-
kafkaBroker	5	48	11	-
ocnaddscpaggregation	2	4	11	SCP=66 (Each instance 6 partition)
ocnaddscpaggregation MESSAGE SEQUENCING =ON DD METADATA = ON/OFF	2	48	14	SCP=84 (Each instance 6 partition)
consumeradapter (HTTP2 feed)	3	24	29	MAIN=261 (Each instance 6 partition)

Note:

• The number of instance for SCP aggregation may increase from defined number in resource profile based on message sequencing timer expiry configuration (using Max timer expiry value) and Transaction success rate.
• Additional memory is required for SCP aggregation service if Metadata Enrichment feature is enabled and value of properties "METADATA_MAP_CACHE_EXPIRY_TIME_MS" and "METADATA_MAP_CACHE_SCHEDULER_TIME_MS" is increased to a higher value.
• End-to-end latency may increase based on "Timer Expiry Value + Processing Time + RF2/RF1 Processing Time + third-party response time (for HTTP2 Feed)."
• More instances of the Kafka broker might be required when running with RF=2, based on setup performance. End-to-end latency might also increase if DISK I/O is slow.
• For DISK I/O refer to Disk Throughput Requirements
• For Kafka PVC-Storage refer to Kafka PVC Storage Requirements

3.1.3.2.2.3 Aggregated 135K MPS Synthetic (TCP) Feed

When Weighted Load Balancing is ON/OFF and Filter is OFF

• Replication Factor: 1
• Message Size: 3500
• Feed Type: Synthetic (TCP)
• FILTER: OFF
• WLB: WLB is ON/OFF

15K NRF Profile

Table 3-34 15K NRF Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
zookeeper	1	1	3	-
kafkaBroker	2	24	3	-
kafkaBroker (with replicated feed)	2	24	3	-
ocnaddnrfaggregation	2	2	1	NRF=6
consumeradapter (Synthethic feed)	3	3	2	MAIN=12

90K SCP Profile

Table 3-35 90K SCP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
zookeeper	1	1	3	-
kafkaBroker	4	48	4	-
kafkaBroker (with replicated feed)	7	48	4	-
ocnaddscpaggregation	2	4	5	SCP=30 (Each Instance 6 partitions)
consumeradapter (Synthethic feed)	3	3	8	MAIN=48

30K SEPP Profile

Table 3-36 30K SEPP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
zookeeper	1	1	3	-
kafkaBroker	3	18	3	-
kafkaBroker (with replicated feed)	6	24	3	-
ocnaddseppaggregation	2	4	2	SEPP=12 (Each Instance 6 partitions)
consumeradapter (Synthethic feed)	3	3	3	MAIN=18

135K Profile (SCP: 90K, NRF: 15K, SEPP: 30K)

Table 3-37 135K Profile (SCP: 90K, NRF: 15K, SEPP: 30K)

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
zookeeper	1	1	3	-
kafkaBroker	6	48	6	-
kafkaBroker (with replicated feed)	7.5	96	6	-
ocnaddscpaggregation	-	-	-	SCP= 30 (Each Instance 6 partitions)
ocnaddnrfaggregation	-	-	-	NRF= 6 (Each Instance 6 partitions)
ocnaddseppaggregation	2	4	2	SEPP=12 (Each Instance 6 partitions)
consumeradapter (Synthethic feed)	3	6	11	MAIN=66 (Each Instance 6 partitions)

135K SCP Profile

Table 3-38 135K SCP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
zookeeper	1	1	3	-
kafkaBroker	6	48	6	-
kafkaBroker (with replicated feed)	6.5	96	6	-
ocnaddscpaggregation	2	4	8	SCP=48 (Each Instance 6 partitions)
consumeradapter (Synthethic feed)	3	6	11	MAIN=66 (Each Instance 6 partitions)

When Weighted Load Balancing is ON/OFF, L3L4 Mapping is ON/OFF, and Filter is ON

• Replication Factor: 1
• Message Size: 3500
• Feed Type: SYNTHETIC
• L3L4 Mapping: ON/OFF
• FILTER: ON
• WLB: WLB is ON/OFF

15K NRF Profile

Table 3-39 15K NRF Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
ocnaddnrfaggregation (Ingress Filter is ON)	2	2	2	NRF=12 (Each Instance 6 partitions)
consumeradapter (Synthethic feed with Egress Filter ON)	3	3	3	MAIN=18

90K SCP Profile

Table 3-40 90K SCP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
ocnaddscpaggregation (Ingress Filter is ON)	2	4	6	SCP=36 (Each Instance 6 partitions)
consumeradapter (Synthethic feed with Egress Filter ON)	3	3	9	MAIN=54

30K SEPP Profile

Table 3-41 30K SEPP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
ocnaddseppaggregation (Ingress Filter is ON)	2	4	3	SEPP=18 (Each Instance 6 partitions)
consumeradapter (Synthethic feed with Egress Filter ON)	3	3	3	MAIN=18

135K Profile (SCP: 90K, NRF: 15K, SEPP: 30K)

Table 3-42 135K Profile (SCP: 90K, NRF: 15K, SEPP: 30K)

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
ocnaddscpaggregation (Ingress Filter is ON)	2	4	6	SCP=36 (Each Instance 6 partitions)
ocnaddnrfaggregation (Ingress Filter is ON)	2	2	2	NRF=12 (Each Instance 6 partitions)
ocnaddseppaggregation (Ingress Filter is ON)	2	4	3	SEPP=18 (Each Instance 6 partitions)
consumeradapter (Synthethic feed with Egress Filter ON)	3	6	11	MAIN=66 (Each Instance 6 partitions)

135K SCP Profile

Table 3-43 135K SCP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
ocnaddscpaggregation (Ingress Filter is ON)	2	4	9	SCP=54 (Each Instance 6 partitions)
consumeradapter (Synthethic feed with Egress Filter ON)	3	6	11	MAIN=66 (Each Instance 6 partitions)

Note:

• When advance OCNADD features like Ingress filtering, Egress filtering. L3-L4 and Weighted load balancing are enabled simultaneously, then resource requirement for "consumeradapter (Synthethic feed)" may vary at higher throughput.
• Resource requirement may vary when Filter is ON based on % data allowed after filtering and number of filter condition with values configured.
• Resource requirement may vary when L3L4 is ON and size of global l3l4 configuration is big.
• Five/Six instances of Kafka broker might require while running RF=2 based on setup performance and end-2-end latency might get increased when DISK I/O is slow,
• For DISK I/O refer to Disk Throughput Requirements
• For Kafka PVC-Storage refer to Kafka PVC Storage Requirements

3.1.3.2.2.4 SCP 270K MPS Synthetic (TCP) Feed

When Weighted Load Balancing is ON/OFF and Filter is OFF

• Replication Factor: 1
• Message Size: 3500
• FEED Type: Synthetic (TCP)
• FILTER: OFF
• WLB: WLB is ON/OFF

Table 3-44 270K MPS SCP Profile

Services	vCPU	Memory Required (Gi)	Total Replica	Topic Partition
zookeeper	1	1	3	-
kafkaBroker	5	48	11	-
ocnaddscpaggregation	2	4	11	SCP=66 (Each instance 6 partition)
ocnaddscpaggregation MESSAGE SEQUENCING =ON DD METADATA = ON/OFF	2	48	14	SCP=84 (Each instance 6 partition)
consumeradapter (Synthethic feed)	3	6	21	MAIN=126 (Each instance 6 partition)

Note:

• Resource requirements may vary when L3L4 is ON, and the size of the global L3L4 configuration is large.
• 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 max timer expiry value) and transaction success rate.
• Additional memory is required for the SCP aggregation service if the Metadata Enrichment feature is enabled, and the values of properties "METADATA_MAP_CACHE_EXPIRY_TIME_MS" and "METADATA_MAP_CACHE_SCHEDULER_TIME_MS" are increased to a higher value.
• End-to-end latency may increase based on "Timer Expiry Value + Processing Time + RF2/RF1 Processing Time + third-party response time (for HTTP2 Feed)."
• More instances of the Kafka broker might be required when running with RF=2, based on setup performance. End-to-end latency might also increase if DISK I/O is slow.
• For DISK I/O refer to Disk Throughput Requirements
• For Kafka PVC-Storage refer to Kafka PVC Storage Requirements

3.1.3.2.2.5 BSF 9K MPS All Feed Types

When Weighted Load Balancing is ON/OFF and Filter is OFF

• Replication Factor: 1
• Message Size: 3500
• FEED Type: ALL
• FILTER: OFF
• WLB: WLB is ON/OFF

Table 3-45 9K MPS BSF Profile

Services	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
zookeeper	1	1	3	-
kafkaBroker	2	24	4	-
ocnaddbsfaggregation	2	2	1	BSF=6
ocnaddbsfaggregation MESSAGE SEQUENCING =ON DD METADATA = ON/OFF	2	16	1	BSF=6
ocnaddconsumeradapter (Synthetic Feed)	3	4	1	MAIN=6
ocnaddconsumeradapter (HTTP2 Feed)	3	4	1	MAIN=9
FEED TYPE = CORRELATED_FILTERED (Minimum 20% data filter is configured)
ocnaddfilter	2	3	1	MAIN=6,<feed-name>-FILTERED=6
ocnaddcorrelation	3	48	1	<feed-name>-FILTERED-CORRELATED=6 or as per consumer

Note:

• Resource requirements may vary for the filter service based on the % of data allowed after filtering and the number of filter conditions with values configured.
• Resource requirements for the correlation service may vary when all messages of a transaction are not received and the value of "maxTransactionWaitTime" is set to a higher value. (It is recommended to have a lower value in these scenarios.)
• Kafka broker resource requirements will increase in the case of rf=2 and/or if replicated feed is running. End-to-end latency might increase when DISK I/O is slow.
• The above resource requirements for the correlation service are mentioned for a single feed; in the case of a replicated feed, additional resources will be required in Kafka.
• Additional memory is required for the aggregation service if the Metadata Enrichment feature is enabled, and the values of properties "METADATA_MAP_CACHE_EXPIRY_TIME_MS" and "METADATA_MAP_CACHE_SCHEDULER_TIME_MS" are increased to a higher value.
• The end-to-end latency may increase based on "Timer Expiry Value + Processing Time + RF2/RF1 Processing Time + third-party response time (for HTTP2 Feed)."
• Filter service memory and CPU requirements may need to increase based on the number of CORRELATED_FILTERED feeds configured; the above requirement is given for a single configuration.
• For DISK I/O refer to Disk Throughput Requirements
• For Kafka PVC-Storage refer to Kafka PVC Storage Requirements
• It is mandatory to create CORRELATED/CORRELATED_FILTERED ACL feeds before making correlation configurations.
• Calculate the PVC size of the Kafka broker in advance for correlation configurations, as each new CORRELATED ACL feed type correlation configuration creates 1 new topic, and each new CORRELATED_FILTERED ACL feed type correlation configuration creates 2 new topics.
• CPU and Memory requirements in Kafka will increase based on the number of configurations of CORRELATED or CORRELATED_FILTERED. Resources are mentioned below for a maximum of 2 configurations.
• Resource requirements for the correlation service may vary when all messages of a transaction are not received and the value of "maxTransactionWaitTime" is set higher. (It is recommended to have a lower value in these scenarios.)

3.1.3.2.2.6 PCF 30K MPS All Feed Types

When Weighted Load Balancing is ON/OFF and Filter is OFF

• Replication Factor: 1
• Message Size: 3500
• FEED Type: ALL
• FILTER: OFF
• WLB: WLB is ON/OFF

Table 3-46 30K MPS PCF Profile

Services	vCPU	Memory Required (Gi)	Total Replica	Topic Partition
zookeeper	1	1	3	-
kafkaBroker	3	24	4	-
ocnaddpcfaggregation	2	2	2	PCF=12
ocnaddpcfaggregation MESSAGE SEQUENCING =ON DD METADATA = ON/OFF	2	24	2	PCF=12
ocnaddconsumeradapter (Synthetic Feed)	3	4	3	MAIN=18
ocnaddconsumeradapter (HTTP2 Feed)	3	4	3	MAIN=27
FEED TYPE = CORRELATED_FILTERED (Minimum 20% data filter is configured)
ocnaddfilter	2	3	4	MAIN=24, <feed-name>-FILTERED=24
ocnaddcorrelation	3	64	4	<feed-name>-FILTERED-CORRELATED=24 or as per consumer

Note:

• Resource requirements may vary for the filter service based on the percentage of data allowed after filtering and the number of filter conditions with configured values.
• Resource requirements for the correlation service may vary when all messages of a transaction are not received and the value of "maxTransactionWaitTime" is set higher. (It is recommended to use a lower value in these scenarios.)
• Kafka broker resource requirements will increase in the case of rf=2 and/or if a replicated feed is running, and end-to-end latency might increase when DISK I/O is slow.
• The above resource requirements for the correlation service are mentioned for a single feed, and in the case of a replicated feed, additional resources will be required in Kafka.
• Additional memory is required for the aggregation service if the Metadata Enrichment feature is enabled and the values of properties "METADATA_MAP_CACHE_EXPIRY_TIME_MS" and "METADATA_MAP_CACHE_SCHEDULER_TIME_MS" are increased.
• End-to-end latency may increase based on "Timer Expiry Value + Processing Time + RF2/RF1 Processing Time + third-party response time (for HTTP2 Feed)."
• Filter service memory and CPU requirements may need to increase based on the number of CORRELATION_FILTERED feeds configured. The above requirements are given for a single configuration.
• For DISK I/O refer to Disk Throughput Requirements
• For Kafka PVC-Storage refer to Kafka PVC Storage Requirements
• It is mandatory to create CORRELATED/CORRELATED_FILTERED ACL feeds before making a correlation configuration.
• Calculate the PVC size of the Kafka broker in advance for correlation configurations, as each new CORRELATED ACL feed type correlation configuration creates 1 new topic, and each new CORRELATED_FILTERED ACL feed type correlation configuration creates 2 new topics.
• CPU and memory requirements in Kafka will increase based on the number of CORRELATED or CORRELATED_FILTERED configurations. Resources are mentioned below for a maximum of 2 configurations.
• Resource requirements for the correlation service may vary when all messages of a transaction are not received and the value of "maxTransactionWaitTime" is set higher. (It is recommended to use a lower value in these scenarios.)

3.1.3.2.2.7 Message Sequencing and Metadata Enrichment 135K MPS All Feed Types

• Replication Factor: 2
• Message Size: 3500
• Feed Type: HTTP2/TCP/KAFKA

Table 3-47 Resource Requirement

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partition
ocnaddkafka (Kafka with RF=2)	6	164	6	-
MESSAGE_SEQUENCING_TYPE = TRANSACTION, TRANSACTION_MSG_SEQUENCING_EXPIRY_TIMER= 200ms and METADATA ENRICHMENT ON/OFF
ocnaddscpaggregation	2	24	5	30(SCP)
MESSAGE_SEQUENCING_TYPE = TIME_WINDOW, WINDOW_MSG_SEQUENCING_EXPIRY_TIMER=10ms
ocnaddscpaggregation	2	24	5	30(SCP)
MESSAGE_SEQUENCING_TYPE = REQUEST_RESPONSE, REQUEST_RESPONSE_MSG_SEQUENCING_EXPIRY_TIMER=10ms and METADATA ENRICHMENT ON/OFF
ocnaddscpaggregation	2	16	5	30(SCP)
INGRESS FILTER is ON
MESSAGE_SEQUENCING_TYPE = TRANSACTION, TRANSACTION_MSG_SEQUENCING_EXPIRY_TIMER= 200ms and METADATA ENRICHMENT ON/OFF
ocnaddscpaggregation	2	36	6	36(SCP)
MESSAGE_SEQUENCING_TYPE = TIME_WINDOW, WINDOW_MSG_SEQUENCING_EXPIRY_TIMER=10ms
ocnaddscpaggregation	2	36	6	36(SCP)
MESSAGE_SEQUENCING_TYPE = REQUEST_RESPONSE, REQUEST_RESPONSE_MSG_SEQUENCING_EXPIRY_TIMER=10ms and METADATA ENRICHMENT ON/OFF
ocnaddscpaggregation	2	24	6	36(SCP)
HTTP2 Feed (FILTER = OFF)
consumeradapter	3	24	15	135(MAIN)
SYNTHETIC Feed (TCP CONNECTION MESSAGE and/or MESSAGE SEGEMENTATION = ON) (FILTER=OFF)
consumeradapter	3	12	11	66(MAIN)

Note:

• Update value of parameter "numIoThreads" to 128 in custom-value.yaml file

• The performance run has been completed with 90% success rate of transactions (Success Trasanction = All 4 message of Transaction ("RxRequest, TxRequest.RxResponse,TxResponse") are received from SCP NF)
• The number of instances for SCP aggregation may increase from defined number in resource profile based on message sequencing timer expiry configuration (using Max timer expiry value) and Transaction success rate.
• Additional memory is required for SCP aggregation service if Metadata Enrichment feature is enabled and value of properties "METADATA_MAP_CACHE_EXPIRY_TIME_MS" and "METADATA_MAP_CACHE_SCHEDULER_TIME_MS" is increased to a higher value.
• The end-2-end latency may increase based on "Timer Expiry Value + Processing Time+ RF2 Processing Time+ 3rd party response time (For HTTP2 Feed)"

3.1.3.2.2.8 Correlated 30K MPS Kafka Feed

Note:

• Creating a CORRELATED or CORRELATED_FILTERED ACL feed is mandatory before making a correlation configuration.
• Calculate the PVC size of a Kafka broker in advance, as each new CORRELATED ACL feed type correlation configuration creates one new topic, and each new CORRELATED_FILTERED ACL feed type correlation configuration creates two new topics.
• The CPU and memory requirement in Kafka increase based on the number of CORRELATED or CORRELATED_FILTERED configurations; the resources mentioned in the below table are for a maximum of two configurations.
• Resource requirements for correlation service vary when all the transaction messages are not received and the value of maxTransactionWaitTime is set to higher value (it is recommended to have a lower value for this scenario).

• Replication Factor: 1
• Message Size: 3500
• Feed Type: CORRELATED

15K NRF Profile

Table 3-48 15K NRF Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
zookeeper	1	1	3	-
kafkaBroker	3	24	4	-
EXPORT/TRACE(1K MPS rate is supported for inbound OCNADD data) for 3 export configuration
ocnaddexport	3	24	1	EXPORT/TRACE (1K MPS rate supported for inbound OCNADD data)
kafkaBroker (with replicated feed )	3	24	4	-
ocnaddnrfaggregation	2	2	1	NRF=6 (Each Instance 6 partitions)
Feed TYPE = CORRELATED
ocnaddcorrelation	3	64	3	MAIN=18, -CORRELATED=18 or as per consumer
Feed TYPE = CORRELATED_FILTERED (Minimum 20% data filter is configured)
ocnaddfilter	2	3	3	MAIN=18, -FILTERED=18
ocnaddcorrelation (Filtered)	3	48	3	-FILTERED-CORRELATED=18 or as per consumer
Per Correlation Feed(1K MPS supported with 24 hours retention)
storageadapter	3	16	1	Per Correlation Feed (1K MPS supported with 24 hours retention)

30K SCP Profile

Table 3-49 30K SCP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
zookeeper	1	1	3	-
kafkaBroker	4	24	4	-
EXPORT/TRACE(1K MPS rate is supported for inbound OCNADD data) for 3 export configuration
ocnaddexport	3	24	1	EXPORT/TRACE (1K MPS rate supported for inbound OCNADD data)
kafkaBroker (with replicated feed)	5	32	4	-
ocnaddscpaggregation	2	2	2	SCP=12 (Each Instance 6 partitions)
Feed TYPE = CORRELATED
ocnaddcorrelation	3	64	4	MAIN=24, -CORRELATED=24 or as per consumer
Feed TYPE = CORRELATED_FILTERED (Minimum 20% data filter is configured)
ocnaddfilter	2	3	4	MAIN=24, -FILTERED=24
ocnaddcorrelation (Filtered)	3	64	4	FILTERED-CORRELATED=24 or as per consumer
Per Correlation Feed(1K MPS supported with 24 hours retention)
storageadapter	3	16	1	Per Correlation Feed (1K MPS supported with 24 hours retention)

30K SEPP Profile

Table 3-50 30K SEPP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
zookeeper	1	1	3	-
kafkaBroker	4	24	4	-
EXPORT/TRACE(1K MPS rate is supported for inbound OCNADD data) for 3 export configuration
ocnaddexport	3	24	1	EXPORT/TRACE (1K MPS rate supported for inbound OCNADD data)
kafkaBroker (with replicated feed)	5	32	4	-
ocnaddseppaggregation	2	2	2	SEPP=12 (Each Instance 6 partitions)
Feed TYPE = CORRELATED
ocnaddcorrelation	3	64	4	MAIN=24, -CORRELATED=24 or as per consumer
Feed TYPE = CORRELATED_FILTERED (Minimum 20% data filter is configured)
ocnaddfilter	2	3	4	MAIN=24, FILTERED=24
ocnaddcorrelation (Filtered)	3	64	4	FILTERED-CORRELATED=24 or as per consumer
Per Correlation Feed(1K MPS supported with 24 hours retention)
storageadapter	3	16	1	Per Correlation Feed (1K MPS supported with 24 hours retention)

30K Profile (SCP: 15K, NRF: 5K, SEPP: 10K)

Table 3-51 30K Profile (SCP: 15K, NRF: 5K, SEPP: 10K)

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
zookeeper	1	1	3	-
kafkaBroker	4	24	4	-
EXPORT/TRACE(1K MPS rate is supported for inbound OCNADD data) for 3 export configuration
ocnaddexport	3	24	1	EXPORT/TRACE (1K MPS rate supported for inbound OCNADD data)
kafkaBroker (with replicated feed)	5	32	4	-
ocnaddscpaggregation	2	2	1	SCP=6 (Each Instance 6 partitions)
ocnaddnrfaggregation	2	2	1	NRF=6 (Each Instance 6 partitions)
ocnaddseppaggregation	2	2	1	SEPP=6 (Each Instance 6 partitions)
Feed TYPE = CORRELATED
ocnaddcorrelation	3	64	4	MAIN=24, -CORRELATED=24 or as per consumer
Feed TYPE = CORRELATED_FILTERED (Minimum 20% data filter is configured)
ocnaddfilter	2	3	4	MAIN=24, FILTERED=24
ocnaddcorrelation (Filtered)	3	64	4	FILTERED-CORRELATED=24 or as per consumer
Per Correlation Feed(1K MPS supported with 24 hours retention)
storageadapter	3	16	1	Per Correlation Feed (1K MPS supported with 24 hours retention)

Note:

• Resource requirement may vary for filter service based on % data allowed after filtering and number of filter condition with values configured.
• Resource requirement for correlation service may vary when all messages of transaction are not received and value of "maxTransactionWaitTime" is set to higher (It is recommended to have lower value for these scenario).
• Kafka broker resource requirement will increase in case of rf=2 and/or replicated feed is running and end-2-end latency might get increased when DISK I/O is slow,
• The above resource requirement of correlation service is mentioned for single feed and in case of replicated feed, Additional resource will be required in kafka.
• Filter service memory and cpu requirement may need to increase based on number of CORRLATION_FILTERED feed is/are configured. Above requirement is given for single configuration.
• For DISK I/O refer to Disk Throughput Requirements
• For Kafka PVC-Storage refer to Kafka PVC Storage Requirements

3.1.3.2.2.9 Aggregated 135K MPS Kafka Feed

• Replication Factor: 1
• Message Size: 3500
• Feed Type: KAFKA

15K NRF Profile

Table 3-52 15K NRF Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
zookeeper	1	1	3	-
kafkaBroker	2	24	3	-
kafkaBroker (with replicated feed)	2	24	3	-
ocnaddnrfaggregation (Ingress FILTER is OFF)	2	2	1	NRF=6 (Each Instance 6 partition)
ocnaddnrfaggregation (Ingress Filter is ON)	2	2	2	NRF=12 (Each Instance 6 partition)

90K SCP Profile

Table 3-53 90K SCP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
zookeeper	1	1	3	-
kafkaBroker	6	24	4	-
kafkaBroker (with replicated feed)	7	48	4	-
ocnaddscpaggregation (Ingress FILTER is OFF)	2	4	5	SCP=30 (Each Instance 6 partition)
ocnaddscpaggregation (Ingress FILTER is OFF)	2	4	6	SCP=36 (Each Instance 6 partition)

30K SEPP Profile

Table 3-54 30K SEPP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
zookeeper	1	1	3	-
kafkaBroker	5	18	3	-
kafkaBroker (with replicated feed)	6	24	3	-
ocnaddseppaggregation (Ingress FILTER is OFF)	2	4	2	SEPP=12 (Each Instance 6 partition)
ocnaddseppaggregation (Ingress Filter is ON)	2	4	3	SEPP=18 (Each Instance 6 partition)

135K Profile (SCP:90K, NRF:15K, SEPP:30K)

Table 3-55 135K Profile (SCP:90K, NRF:15K, SEPP:30K)

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
zookeeper	1	1	3	-
kafkaBroker	6.5	48	6	-
kafkaBroker (with replicated feed)	7.5	96	6	-
ocnaddscpaggregation (Ingress FILTER is OFF)	2	4	5	SCP=30 (Each Instance 6 partition)
ocnaddnrfaggregation (Ingress FILTER is OFF)	2	2	1	NRF=6 (Each Instance 6 partition)
ocnaddseppaggregation (Ingress FILTER is OFF)	2	4	2	SEPP=12 (Each Instance 6 partition)
ocnaddscpaggregation (Ingress Filter is ON)	2	4	6	SCP=36 (Each Instance 6 partition)
ocnaddnrfaggregation (Ingress Filter is ON)	2	2	2	NRF=12 (Each Instance 6 partition)
ocnaddseppaggregation (Ingress Filter is ON)	2	4	3	SEPP=18 (Each Instance 6 partition)

135K SCP Profile

Table 3-56 135K SCP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
zookeeper	1	1	3	-
kafkaBroker	6.5	48	6	-
kafkaBroker (with replicated feed)	7.5	96	6	-
ocnaddscpaggregation (Ingress FILTER is OFF)	2	4	8	SCP=48 (Each Instance 6 partition)
ocnaddscpaggregation (Ingress Filter is ON)	2	4	9	SCP=54 (Each Instance 6 partition)

Note:

The number of partitions for MAIN topic can be configured similar to the partition count recommended for Synthetic Feed. However, the partition count may increase or decrease as per the design of consumer application.

3.1.3.2.2.10 SCP 270K MPS Kafka Feed

When Weighted Load Balancing is ON/OFF and Filter is OFF

• Replication Factor: 1
• Message Size : 3500
• FEED Type: KAFKA
• FILTER: OFF
• WLB: WLB is ON/OFF

Table 3-57 270K MPS KAFKA FEED

Services	vCPU	Memory Required (Gi)	Total Replica	Topic Partition
zookeeper	1	1	3	-
kafkaBroker	5	48	11	-
ocnaddscpaggregation	2	4	11	SCP=66 (Each instance 6 partition)
ocnaddscpaggregation MESSAGE SEQUENCING =ON DD METADATA = ON/OFF	2	48	14	SCP=84 (Each instance 6 partition)

Note:

• The number of instance for SCP aggregation may increase from defined number in resource profile based on message sequencing timer expiry configuration (using Max timer expiry value) and Transaction success rate.
• Additional memory is required for SCP aggregation service if Metadata Enrichment feature is enabled and value of properties "METADATA_MAP_CACHE_EXPIRY_TIME_MS" and "METADATA_MAP_CACHE_SCHEDULER_TIME_MS" is increased to a higher value.
• End-to-end latency may increase based on "Timer Expiry Value + Processing Time+ RF2/RF1 Processing Time
• More instances of the Kafka broker might be required when running with RF=2, based on setup performance. End-to-end latency might also increase if DISK I/O is slow.
• For DISK I/O refer to Disk Throughput Requirements
• For Kafka PVC-Storage refer to Kafka PVC Storage Requirements

3.1.3.2.2.11 5K MPS Non-Oracle Network Function Feed

• Replication Factor: 1
• Message Size: 3500
• Feed Type: Non-Oracle Network Function Feed

Table 3-58 Resource Requirement

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partitions
ocnaddingressadapter	3	8	1	-
zookeeper	1	1	3	-
ocnaddnonoracleaggregation	2	2	1	NON_ORACLE=6
kafkaBroker	2	16	3	-
consumeradapter	3	6	1	MAIN=9
kafkaBroker (with replicated feed)	2	24	3	-
consumeradapter	3	6	2	MAIN=18

3.1.3.2.2.12 Resource Profile for Default Deployment

This profile can stream NFs (SCP, NRF, SEPP) data up to 15K MPS and can be scaled to handle up to 100K MPS for HTTP2 feed when weighted_lb and Filter (Ingress and Egress) are "OFF".

Replication Factor should be "1" and the incoming message size on OCNADD should be less than or equal to 3500K.

• Replication Factor: 1
• Message Size: 3500
• Feed Type: HTTP2, SYNTHETIC

Replication Factor should be 1 and the incoming message size on OCNADD should be less than or equal to 3500K.

Table 3-59 Default Deployment Profile

Services	vCPU Req	vCPU Limit	Memory Req (Gi)	Memory Limit (Gi)	Min Replica	Max Replica	Partitions	Topic Name
ocnaddconfiguration	1	1	1	1	1	1	-	-
ocnaddalarm	1	1	1	1	1	1	-	-
ocnaddadmin	1	1	1	1	1	1	-	-
ocnaddhealthmonitoring	1	1	1	1	1	1	-	-
ocnaddscpaggregation (55K)	2	2	4	4	1	4	24	SCP
ocnaddnrfaggregation (15K)	2	2	2	2	1	1	6	NRF
ocnaddseppaggregation (30K)	2	2	4	4	1	2	12	SEPP
ocnaddbsfaggregation(9K)	2	2	4	4	1	1	6	BSF
ocnaddpcfaggregation(30K)	2	2	4	4	1	2	12	PCF
consumeradapter	3	3	6	6	HTTP2: 2 SYNTHETIC: 1	HTTP2: 13 SYNTHETIC: 9	117	MAIN
kafkaBroker	6	6	48	48	4	4	-	-
zookeeper	1	1	1	2	3	3	-	-
ocnaddgui	1	2	1	1	1	1	-	-
ocnadduirouter	1	2	1	1	1	1	-	-

Note:

• Four instances of Kafka brokers might be required when running Replication Factor rf=2, based on the setup performance. The end-to-end latency might increase when DISK I/O is slow.
• For DISK I/O, see Disk Throughput Requirements.
• For Kafka PVC-Storage, see Kafka PVC Storage Requirements.

3.1.3.3 Resource Profile for OCI Environment

This section displays the profile resource requirements in OCI environment.

3.1.3.3.1 Profile Resource Requirements for HTTP2 Feed for 5K MPS in OCI Environment

The following table displays the profile resource requirements for HTTP2 feed in OCI environment.

Note:

• This test is performed without enabling the Ingress or Egress features.
• The replicated HTTP2 feed's end-to-end latency is between 2ms to 8ms.
• The single HTTP2 feed's end-to-end latency is between 1ms to 3ms.

• Replication Factor = 1
• Message Size = 3500
• Feed Type: HTTP2

5K Profile (SCP:3K NRF:1K SEPP:1K)

Table 3-60 5K Profile (SCP:3K NRF:1K SEPP:1K)

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partition
ocnaddconfiguration	1	1	1	-
ocnaddalarm	1	1	1	-
ocnaddadmin	1	1	1	-
ocnaddhealthmonitoring	1	1	1	-
ocnaddgui	2	1	1	-
ocnadduirouter	2	1	1	-
zookeeper	1	1	3	-
ocnaddkafka	2	24	4	-
Replicated Feed (Avg Latency: 1ms)
ocnaddkafka	3	32	4	-
Single Feed (Avg Latency: 1ms)
ocnaddscpaggregation	2	2	1	SCP=6 (Each Instance 6 partition)
ocnaddnrfaggregation	2	2	1	NRF=6 (Each Instance 6 partition)
ocnaddseppaggregation	2	2	1	SEPP=12 (Each Instance 6 partition)
ocnaddadapter	3	3	2	MAIN=18 (Each instance 9 partition)

5K SCP Profile

Table 3-61 5K SCP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partition
ocnaddconfiguration	1	1	1	-
ocnaddalarm	1	1	1	-
ocnaddadmin	1	1	1	-
ocnaddhealthmonitoring	1	1	1	-
ocnaddgui	2	1	1	-
ocnadduirouter	2	1	1	-
zookeeper	1	1	3	-
ocnaddkafka	2	24	4	-
Replicated Feed (Avg Latency: 1ms)
ocnaddkafka	3	32		-
Single Feed (Avg Latency: 1ms)
ocnaddscpaggregation	2	2	2	SCP=12 (Each instance 6 partition)
ocnaddnrfaggregation	-	-	-	-
ocnaddseppaggregation	-	-	-	-
ocnaddadapter	3	3	2	MAIN=18 (Each instance 9 partition)

3.1.3.3.2 Profile Resource Requirements for Aggregated Kafka Feed for 5K MPS in OCI Environment

The following table displays the profile resource requirements for Aggregated feed in OCI environment.

Note:

• This test is performed without enabling the Ingress or Egress features.

• Replication Factor: 1
• Message Size: 3500
• Feed Type: AGGREGATED KAFKA

5K Profile (SCP:3K NRF:1K SEPP:1K)

Table 3-62 5K Profile (SCP:3K NRF:1K SEPP:1K)

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partition
ocnaddconfiguration	1	1	1	-
ocnaddalarm	1	1	1	-
ocnaddadmin	1	1	1	-
ocnaddhealthmonitoring	1	1	1	-
ocnaddgui	2	1	1	-
ocnadduirouter	2	1	1	-
zookeeper	1	1	3	-
ocnaddkafka	2	24	4	-
Replicated Feed
ocnaddkafka	3	32		-
Single Feed
ocnaddscpaggregation	2	2	1	SCP=6 (Each Instance 6 partition)
ocnaddnrfaggregation	2	2	1	NRF=6 (Each Instance 6 partition)
ocnaddseppaggregation	2	2	1	SEPP=12 (Each Instance 6 partition)

5K SCP Profile

Table 3-63 5K SCP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partition
ocnaddconfiguration	1	1	1	-
ocnaddalarm	1	1	1	-
ocnaddadmin	1	1	1	-
ocnaddhealthmonitoring	1	1	1	-
ocnaddgui	2	1	1	-
ocnadduirouter	2	1	1	-
zookeeper	1	1	3	-
ocnaddkafka	2	24	4	-
Replicated Feed
ocnaddkafka	3	32		-
Single Feed
ocnaddscpaggregation	2	2	2	SCP=12 (Each instance 6 partition)
ocnaddnrfaggregation	-	-	-	-
ocnaddseppaggregation	-	-	-	-

3.1.3.3.3 Profile Resource Requirements for Synthetic Feed for 5K MPS in OCI Environment

The following table displays the profile resource requirements for Synthetic feed in OCI environment.

Note:

• This test is performed without enabling the Ingress or Egress features.
• The replicated TCP feed's end-to-end average latency is 3ms. The Block Volume Performance is 50% Balanced and 50% High Performance.
• The single TCP feed's end-to-end average latency is 3ms. The Block Volume Performance is "Balanced".

• Replication Factor: 1
• Message Size = 3500
• Feed Type: TCP

5K Profile (SCP:3K NRF:1K SEPP:1K)

Table 3-64 5K Profile (SCP:3K NRF:1K SEPP:1K)

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partition
ocnaddconfiguration	1	1	1	-
ocnaddalarm	1	1	1	-
ocnaddadmin	1	1	1	-
ocnaddhealthmonitoring	1	1	1	-
ocnaddgui	2	1	1	-
ocnadduirouter	2	1	1	-
zookeeper	1	1	3	-
ocnaddkafka	3	24	4	-
Replicated Feed (Avg Latency: 0.3ms)
ocnaddkafka	4	32	4	-
Single Feed (Avg Latency: 0.3ms)
ocnaddscpaggregation	2	2	1	SCP=6 (Each Instance 6 partition)
ocnaddnrfaggregation	2	2	1	NRF=6 (Each Instance 6 partition)
ocnaddseppaggregation	2	2	1	SEPP=12 (Each Instance 6 partition)
ocnaddadapter	3	3	2	MAIN=12 (Each instance 6 partition)

5K SCP Profile

Table 3-65 5K SCP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partition
ocnaddconfiguration	1	1	1	-
ocnaddalarm	1	1	1	-
ocnaddadmin	1	1	1	-
ocnaddhealthmonitoring	1	1	1	-
ocnaddgui	2	1	1	-
ocnadduirouter	2	1	1	-
zookeeper	1	1	3	-
ocnaddkafka	3	24	4	-
Replicated Feed (Avg Latency: 0.3ms)
ocnaddkafka	4	32	4	-
Single Feed (Avg Latency: 0.3ms)
ocnaddscpaggregation	2	2	2	SCP=12 (Each instance 6 partition)
ocnaddnrfaggregation	-	-	-	-
ocnaddseppaggregation	-	-	-	-
ocnaddadapter	3	3	2	MAIN=12 (Each instance 6 partition)

3.1.3.3.4 Profile Resource Requirements for Correlated Kafka Feed for 5K MPS in OCI Environment

The following table displays the profile resource requirements for Correlated Kafka feed in OCI environment.

• Replication Factor: 1
• Message Size: 3500
• ACL Feed Type: CORRELATED

5K Profile (SCP:3K NRF:1K SEPP:1K)

Table 3-66 5K Profile (SCP:3K NRF:1K SEPP:1K)

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partition
ocnaddconfiguration	1	1	1	-
ocnaddalarm	1	1	1	-
ocnaddadmin	1	1	1	-
ocnaddhealthmonitoring	1	1	1	-
ocnaddgui	2	1	1	-
ocnadduirouter	2	1	1	-
zookeeper	1	2	3	-
ocnaddkafka	3	32	4	-
Feed TYPE = CORRELATED
ocnaddscpaggregation	2	2	2	SCP=12 (Each instance 6 partition)
ocnaddnrfaggregation	-	-	-	-
ocnaddseppaggregation	-	-	-	-
ocnaddcorrelation	3	24	3	MAIN=18,<feed-name>-CORRELATED=18 or as per consumer
Feed TYPE = CORRELATED_FILTERED (Minimum 20% data filter is configured)
ocnaddfilter	2	3	3	MAIN=18,<feed-name>-FILTERED=18
ocnaddcorrelation	2	16	3	<feed-name>-FILTERED-CORRELATED=18 or as per consumer

5K SCP Profile

Table 3-67 5K SCP Profile

Service	vCPU	Memory Required (Gi)	Total Replica	Topic Partition
ocnaddconfiguration	1	1	1	-
ocnaddalarm	1	1	1	-
ocnaddadmin	1	1	1	-
ocnaddhealthmonitoring	1	1	1	-
ocnaddgui	2	1	1	-
ocnadduirouter	2	1	1	-
zookeeper	1	1	3	-
ocnaddkafka	3	32	4	-
Feed TYPE = CORRELATED
ocnaddscpaggregation	2	2	1	SCP=6 (Each Instance 6 partition)
ocnaddnrfaggregation	2	2	1	NRF=6 (Each Instance 6 partition)
ocnaddseppaggregation	2	2	1	SEPP=12 (Each Instance 6 partition)
ocnaddcorrelation	3	24	3	MAIN=18,<feed-name>-CORRELATED=18 or as per consumer
Feed TYPE = CORRELATED_FILTERED (Minimum 20% data filter is configured)
ocnaddfilter	2	3	3	MAIN=18,<feed-name>-FILTERED=18
ocnaddcorrelation	2	16	3	<feed-name>-FILTERED-CORRELATED=18 or as per consumer

Note:

• The filter service's resource requirements may vary based on the percentage of data allowed post-filtering and the number of filter conditions with configured values.
• The correlation service's resource requirements may vary when all transaction messages are not received and the value of "maxTransactionWaitTime" is set to a higher value (Use a lower value for such scenarios).
• The Kafka broker's resource requirement increases if the Replication Factor is "2" and (or) the Replicated Feed is running, and the end-to-end latency increases when DISK I/O is slow.
• The resource requirement in the above table is for a single feed. Additional Kafka resources are required for replicated feeds.
• Depending on the number of CORRLATION_FILTERED feeds configured, you might have to increase the filter service memory and CPU requirements. The requirements mentioned in the above table are for a single configuration.

3.2 Pod Affinity (or Anti-affinity) Rules

In the Data Director, support for node affinity has been added. The rules are currently defined for the services mentioned in the table below. The rules are currently disabled; however, the user can enable them for the supported services. The rules are provided to control the deployment of certain traffic processing services on a particular set of identified nodes.

Services name:

• Consumer Adapter
• Kafka
• ocnaddnrfaggregation
• ocnaddscpaggregation
• ocnaddseppaggregation
• ocnaddnonoracleaggregation
• ocnaddbsfaggregation
• ocnaddpcfaggregation

Node Affinity Rules

1. Step1: Update the "affinity" section in the ocnadd-custom-values.yaml file

   affinity: {}
                   # Node Affinity Configuration:
                   #
                   # To enable node affinity, remove the empty curly braces ({}) above and un-comment the nodeAffinity section below.
                   # This allows you to specify rules for scheduling pods on specific nodes.
                   #
                   # Example Configuration:
                   ###################################   
                   # nodeAffinity:
                   #   requiredDuringSchedulingIgnoredDuringExecution:
                   #     nodeSelectorTerms:
                   #     - matchExpressions:
                   #       - key: kubernetes.io/hostname
                   #         operator: NotIn
                   #         values:
                   #         - k8s-node-26
                   #         - k8s-node-24
                   #       - key: kubernetes.io/hostname
                   #         operator: In
                   #         values:
                   #         - k8s-node-2
                   #         - k8s-node-3   
                   ###########################################
                   # Explanation:
                   #
                   # - The 'NotIn' expression prevents pods from being scheduled on nodes k8s-node-26 and k8s-node-24.
                   # - The 'In' expression ensures pods are scheduled on nodes k8s-node-2 and k8s-node-3.
                   #
                   # To customize, modify the 'key', 'operator', and 'values' fields according to your needs.
                   # You can add or remove 'matchExpressions' to create more complex scheduling rules.
                   #
                   # Remember to remove the empty 'affinity: {}' and un-comment the desired nodeAffinity configuration to enable it.

2. Helm upgrade the corresponding worker group or the default group

   helm upgrade <source-release-name> -f ocnadd-custom-values-<worker-group>.yaml --namespace <source-release-namespace> <target-release-helm-chart>

   Where,

   • <source-release-name> is the release name of the source release deployment.
   • ocnadd-custom-values-<worker-group>.yaml is the custom values file created for default-worker-group or the Worker Group in separate namespace.
   • <source-release-namespace> is the OCNADD namespace of the source release.
   • <target-release-helm-chart> is the location of the Helm chart of the target release.
   For example:

   helm upgrade ocnadd -f ocnadd-custom-values-wg.yaml --namespace ocnadd-deploy ocnadd_wg

3. Verify that PODs of the modified services have been deployed as per the configured affinity rules.

3.3 Ephemeral Storage Requirements

The following table describes the Ephemeral Storage requirements for OCNADD:

Table:Ephemeral Storage

Table 3-68 Ephemeral Storage Requirements

Service Name	Ephemeral Storage (Request) in Mi	Ephemeral Storage (Limit) in Mi	Description
OAM Services
ocnaddadminservice	200	200	-
ocnaddalarm	100	500	-
ocnaddhealthmonitoring	100	500	-
ocnaddconfiguration	100	500	-
ocnadduirouter	500	500	-
ocnaddexport	1000	2000	-
ocnaddredundancyagent	100	500	Required only when Geo Redundancy is enabled for OCNADD
Worker Group Services
<app-name>-adapter (consumeradapter)	1000	1000	-
ocnaddscpaggregation	100	500	-
ocnaddseppaggregation	100	500	-
ocnaddnrfaggregation	100	500	-
ocnaddbsfaggregation	100	500	-
ocnaddpcfaggregation	100	500	-
ocnaddnonoracleaggregation	100	500	Required only when Data processing is enabled from Non-oracle NFs
ocnaddcorrelation	400	800	-
ocnaddstorageadapter	400	800	-
ocnaddingressadapter	400	800	-
ocnaddfilter	100	800	Required only when "Filtered" or "Correlated Filtered" feed is created

3.4 Disk Throughput Requirements

The following table describes the disk throughput requirements in OCNADD:

Table 3-69 Disk Throughput Requirements

Avg Size (in Bytes)	Rate	RF (Kafka Replication Factor)	Topic (NF+MAIN)	Consumer Feed	Total Write Throughput (MB/s)	Total Read Throughput (MB/s)	No. of Broker	Per Broker Write Throughput (MB/s)	Per Broker Read Throughput (MB/s)	Total per Broker Throughput (MB/s) with 10% buffer	Total Disk Throughput (MB/s) for the Cluster with 10% Buffer
1941	39000	1	2	1	145	145	3	54	54	108	324
1941	39000	2	2	1	289	289	3	106	106	212	636
3769	39000	1	2	1	281	281	3	104	104	208	624
3769	39000	2	2	1	561	561	3	206	206	412	1236

Note:

• The average size of OCNADD Ingress message captured in the table includes the size of metadata list + header list of original 5G HTTP2 header frame + 5G-SBI-Message.
• Currently, it is recommended to set the Replication Factor (RF) value to 1 with the assumption that the underlying storage provides data redundancy. RF value of "2" will be supported in a future release.

The disk throughput calculations are as follows:

Writes: W * RF * T    
Reads: ((RF*T)+C- 1) * W    
Disk Throughput (Write + Read): (W * RF *T) + (L * W)
W -> MB/sec of data that will be written                
RF -> Replication factor                
T   -> No of topics to which data copied. As of now, each message will be copied into two topics.                
C   -> Number of consumer groups, that is the number of readers for each write                
L   -> (RF*T) + C -1

Average Message in Table:

Average Message Size= (a1b1+a2b2+..+a(n)b(n))/(a1+a2+..+a(n))  
a1   -> SCP MPS    
b1   -> SCP message size    
a2   -> NRF MPS    
b2   -> NRF message size    
a(n) -> NF(n) MPS    
b(n) -> NF(n) message size    

Example:

Average message size for row 1 = ((1624*30000)+(3000*9000))/(30000+9000) = 1941 Bytes (approx)

Average message size for row 4 = ((4000*30000)+(3000*9000))/(30000+9000) = 3769 Bytes (approx)

The following table describes the disk throughput for SCP and NRF:

Table 3-70 SCP, NRF, and SEPP Disk Throughput

SCP Message		NRF Message	SEPP Message		RF (Kafka Replication Factor)	Topic (NF+MAIN)	Consumer Feed	Total Write Throughput (MB/s)	Total Read Throughput (MB/s)	No.of Broker	Per Broker Write Throughput (MB/s)	Per Broker Read Throughput (MB/s)	Total per Broker Throughput (MB/s) with 10% buffer	Total Disk Throughput (MB/s) for Cluster with 10% Buffer
Avg Size (Bytes)	Rate	Avg Size (Bytes)	Rate	Avg Size (Bytes)											Rate
1624	30000	3000	9000	3000	15000	1	2	1	145	145	3	54	54	108	324
1624	30000	3000	9000	3000	15000	2	2	1	289	289	3	106	106	212	636
4000	30000	3000	9000	3000	15000	1	2	1	281	281	3	104	104	208	624
4000	30000	3000	9000	3000	15000	2	2	1	561	561	3	206	206	412	1236

Note:

• The average size of OCNADD Ingress message captured in the table includes the size of metadata list + header list of original 5G HTTP2 header frame + 5G-SBI-Message.
• Currently, it is recommended to set the Replication Factor (RF) value to 1 with the assumption that the underlying storage provides data redundancy.

3.5 Kafka PVC Storage Requirements

The following table describes the retention period per topic for different NFs:

Table 3-71 Retention Period Per Topic

Topic Name	Retention Period
SCP	5 Minutes
NRF	5 Minutes
SEPP	5 Minutes
BSF	5 Minutes
PCF	5 Minutes
MAIN	6 Hours (Max)

The following calculation is for storage requirements for a topic:

Important:

For the 6 hrs storage in the MAIN topic, the storage requirement must be calculated using the following information:

Storage Requirement for a topic = MPS * Retention Period * RF * Average Message Size

Where,

MPS is "Message Per Second"

RF is "Replication Factor"

Examples:

1. Average Message Size = 1941 Bytes

   The following example uses the values from the first row of the Table 3-70 table. For more information about the table, see Disk Throughput Requirements:

   Storage Requirement for SCP and NRF Topics = MPS * Retention Period * RF * Message Size = 39000 * 5 Minutes * 3 * 1941
                                                                                  = 39000 * 5 * 60 * 3 * 1941
                                                                                  = ~ 63.45 GB
   Storage Requirement for MAIN = MPS * Retention Period * RF * Message Size  =  39000 * 6 Hours * 3 * 1941
                                                                                  =  39000 * 6 * 60 * 60 * 3 * 1941
                                                                                  =  ~ 4.46 TB
   Total Storage Requirement for the Broker Cluster = Storage for SCP + Storage for NRF + Storage for MAIN
                                                                                  = 63.45 GB + 4.46 TB
                                                                                  = ~ 4.53 TB
   Total Storage for each broker = (4.53/Number of Brokers) TB = (4.53/3) TB = ~ 1.51 TB [Assuming 3 Broker cluster]

2. Average Message Size = 3769 Bytes

   The following example uses the values from the fourth row of the Table 3-70 table. For more information about the table, see Disk Throughput Requirements:

   Storage Requirement for SCP and NRF Topics = MPS * Retention Period * RF * Message Size = 39000 * 5 Minutes * 3 * 3769
                                                                                           = 39000 * 5 * 60 * 3 * 3769
                                                                                           = ~ 123.20 GB
   
   Storage Requirement for MAIN = MPS * Retention Period * RF * Message Size  =  39000 * 6 Hours * 3 * 3769
                                                                                           =  39000 * 6 * 60 * 60 * 3 * 3769
                                                                                           = ~ 8.66 TB
   Total Storage Requirement for the Broker Cluster = Storage for SCP + Storage for NRF + Storage for MAIN
                                                                                           = 123.20 GB + 8.66 TB
                                                                                           = ~ 8.79 TB
   Total Storage for each broker = (8.79/Number of Brokers) TB = (8.79/3) TB = ~ 2.93 TB [Assuming 3 Broker cluster]