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.
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 | Replica | vCPU | Memory | ||
|---|---|---|---|---|---|
| Min | Max | Min | Max | ||
|
SQL (ndbmysqld) Kubernetes Resource Type: StatefulSet |
0 | 1 | 1 | 1Gi | 1Gi |
|
SQL (ndbappmysqld) Kubernetes Resource Type: Statefulset |
2 | 1 | 1 | 1Gi | 1Gi |
|
MGMT (ndbmgmd) Kubernetes Resource Type: StatefulSet |
2 | 1 | 1 | 1Gi | 1Gi |
|
Database (ndbmtd) Kubernetes Resource Type: StatefulSet |
2 | 1 | 1 | 4Gi | 4Gi |
|
Backup Manager Service (db-backup-manager-svc) Kubernetes Resource Type: Deployment |
1 | 0.1 | 0.1 | 128Mi | 128Mi |
|
Monitor Service (db-monitor-svc) Kubernetes Resource Type: Deployment |
1 | 0.2 | 0.2 | 500Mi | 500Mi |
|
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 |
4 | 8 | 8 | 128Gi | 128Gi |
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 | Resources | Description | ||
| vCPU | Memory Required (Gi) | Total Replica | ||
| 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 Resource Profile for Correlated Kafka Feed for 30K MPS. |
| 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 Resource Profile for HTTP2 Feed for 135K MPS
- Replication Factor: 1
- Message Size: 3500
- Feed Type: HTTP2
Table 3-5 Resource Requirement
| Service | 15K NRF Profile | 90K SCP Profile | 30K SEPP Profile | 135K Profile (SCP:90K NRF:15K SEPP:30K) | 135K SCP Profile | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| vCPU | Total Replica | Memory Required (Gi) | Topic Partitions | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | |
| zookeeper | 1 | 3 | 1 | 1 | 3 | 1 | 1 | 3 | 1 | 1 | 3 | 1 | 1 | 3 | 1 | |||||
| ocnaddkafka | 2 | 3 | 24 | 6 | 4 | 48 | 5 | 3 | 18 | 6.5 | 6 | 48 | 6.5 | 6 | 48 | |||||
| Replicated Feed | ||||||||||||||||||||
| ocnaddkafka | 2 | 3 | 24 | 7 | 4 | 48 | 6 | 3 | 24 | 7.5 | 6 | 96 | 7.5 | 6 | 96 | |||||
| WLB is ON/OFF, FILTER is OFF | ||||||||||||||||||||
| ocnaddscpaggregation | - | - | - | - | 2 | 5 | 4 | SCP=30 | - | - | - | - | 2 | 5 | 4 |
SCP=30 (Each Instance 6 partition) |
2 | 8 | 4 |
SCP=48 (Each instance 6 partition) |
| ocnaddnrfaggregation | 2 | 1 | 2 | NRF=6 | - | - | - | - | - | - | - | - | 2 | 1 | 2 |
NRF=6 (Each Instance 6 partition) |
- | - | - | - |
| ocnaddseppaggregation | - | - | - | - | - | - | - | - | 2 | 2 | 4 | SEPP=12 | 2 | 2 | 4 |
SEPP=12 (Each Instance 6 partition) |
- | - | - | - |
| ocnaddadapter | 3 | 2 | 3 | MAIN=18 | 3 | 10 | 16 | MAIN=90 | 3 | 4 | 8 | MAIN=36 | 3 | 15 | 24 |
MAIN=135 (Each instance 9 partition) |
3 | 15 | 24 |
MAIN=135 (Each instance 9 5 partition) |
When Weighted Load Balancing is ON/OFF and Filter is ON
Table 3-6 Resource Requirement
| SERVICE | 15K NRF Profile | 90K SCP Profile | 30K SEPP Profile | 135K Profile (SCP:90K NRF:15K SEPP:30K) | 135K SCP Profile | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| vCPU | Total Replica | Memory Required (Gi) | Topic Partitions | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | |
| Ingress Filter is ON | ||||||||||||||||||||
| ocnaddscpaggregation | - | - | - | - | 2 | 6 | 4 | SCP=36 | - | - | - | - | 2 | 6 | 4 |
SCP=36 (Each Instance 6 partition) |
2 | 9 | 4 |
SCP=54 (Each instance 6 partition) |
| ocnaddnrfaggregation | 2 | 2 | 2 | NRF=12 | - | - | - | - | - | - | - | - | 2 | 2 | 2 |
NRF=12 (Each Instance 6 partition) |
- | - | - | - |
| ocnaddseppaggregation | - | - | - | - | - | - | - | - | 2 | 3 | 2 | SEPP=18 | 2 | 3 | 4 |
SEPP=18 (Each Instance 6 partition) |
- | - | - | - |
| Egress Filter is ON | ||||||||||||||||||||
| ocnaddadapter | 3 | 3 | 3 | MAIN=27 | 3 | 11 | 3 | MAIN=99 | 3 | 5 | 3 | MAIN=45 | 3 | 16 | 24 |
MAIN=144 (Each instance 9 partition) |
3 | 16 | 24 |
MAIN=144 (Each instance 9 partition) |
Note:
- When advanced features such as Ingress filtering, Egress filtering, and Weighted load balancing are enabled simultaneously, the resource requirement for "ocnaddadapter" 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 Resource Profile for Synthetic Feed For 135K MPS
- Replication Factor: 1
- Message Size: 3500
- Feed Type: SYNTHETIC
Table 3-7 Resource Requirement
| Service | 15K NRF Profile | 90K SCP Profile | 30K SEPP Profile | 135K Profile (SCP:90K NRF:15K SEPP:30K) | 135K SCP Profile | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| vCPU | Total Replica | Memory Required (Gi) | Topic Partitions | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | |
| zookeeper | 1 | 3 | 1 | 1 | 3 | 1 | 1 | 3 | 1 | 1 | 3 | 1 | 1 | 3 | 1 | |||||
| ocnaddkafka | 2 | 3 | 24 | 6 | 4 | 48 | 5 | 3 | 18 | 6.5 | 6 | 48 | 6.5 | 6 | 48 | |||||
| Replicated Feed | ||||||||||||||||||||
| ocnaddkafka | 2 | 3 | 24 | 7 | 4 | 48 | 6 | 3 | 24 | 7.5 | 6 | 96 | 7.5 | 6 | 96 | |||||
| WEIGHTED-LB is ON/OFF, L3L4 Mapping is ON/OFF and FILTER is OFF | ||||||||||||||||||||
| ocnaddscpaggregation | - | - | - | - | 2 | 5 | 4 | SCP=30 | - | - | - | - | 2 | 5 | 4 |
SCP=30 (Each Instance 6 partition) |
2 | 8 | 4 |
SCP=48 (Each instance 6 partition) |
| ocnaddnrfaggregation | 2 | 1 | 2 | NRF=6 | - | - | - | - | - | - | - | - | 2 | 1 | 2 |
NRF=6 (Each Instance 6 partition) |
- | - | - | - |
| ocnaddseppaggregation | - | - | - | - | - | - | - | - | 2 | 2 | 4 | SEPP=12 | 2 | 2 | 4 |
SEPP=12 (Each Instance 6 partition) |
- | - | - | - |
| ocnaddadapter | 3 | 2 | 3 | MAIN=12 | 3 | 8 | 3 | MAIN=48 | 3 | 3 | 3 | MAIN=18 | 3 | 11 | 6 |
MAIN=66 (Each instance 6 partition) |
3 | 11 | 6 |
MAIN=66 (Each instance 6 partition) |
When Weighted Load Balancing is ON/OFF, L3L4 Mapping is ON/OFF, and Filter is ON
Table 3-8 Resource Requirement
| Service | 15K NRF Profile | 90K SCP Profile | 30K SEPP Profile | 135K Profile (SCP:90K NRF:15K SEPP:30K) | 135K SCP Profile | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| vCPU | Total Replica | Memory Required (Gi) | Topic Partitions | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | |
| Ingress Filter is ON | ||||||||||||||||||||
| ocnaddscpaggregation | - | - | - | - | 2 | 6 | 4 | SCP=36 | - | - | - | - | 2 | 6 | 4 |
SCP=36 (Each Instance 6 partition) |
2 | 9 | 4 |
SCP=54 (Each Instance 6 partition) |
| ocnaddnrfaggregation | 2 | 2 | 2 | NRF=12 | - | - | - | - | - | - | - | - | 2 | 2 | 2 |
NRF=12 (Each Instance 6 partition) |
- | - | - | - |
| ocnaddseppaggregation | - | - | - | - | - | - | - | - | 2 | 3 | 4 | SEPP=18 | 2 | 3 | 4 |
SEPP=18 (Each Instance 6 partition) |
- | - | - | - |
| Egress Filter is ON | ||||||||||||||||||||
| ocnaddadapter | 3 | 3 | 3 | MAIN=18 | 3 | 9 | 3 | MAIN=54 | 3 | 3 | 3 | MAIN=18 | 3 | 11 | 6 |
MAIN=66 (Each instance 6 partition) |
3 | 11 | 6 |
MAIN=66 (Each instance 6 partition) |
Note:
- When advance OCNADD features like Ingress filtering, Egress filtering. L3-L4 and Weighted load balancing are enabled simultaneously, then resource requirement for "ocnaddadapter" 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.3 Resource Profile for Synthetic Feed For 270K MPS
270K MPS SCP Profile
- Replication Factor: 1
- Message Size : 3500
- FEED Type: SYNTHETIC
- FILTER: OFF
Table 3-9 270K MPS SCP Profile
| Services | vCPU | Total Replica | Memory Required (Gi) | Topic Partition |
|---|---|---|---|---|
| zookeeper | 1 | 3 | 1 | - |
| ocnaddkafka | 5 | 11 | 48 | - |
| ocnaddscpaggregation | 2 | 11 | 4 |
SCP=66 (Each instance 6 partition) |
| MESSAGE SEQUENCING =ON and DD METADATA = ON/OFF | ||||
| ocnaddscpaggregation | 2 | 14 | 48 |
SCP=84 (Each instance 6 partition) |
| ocnaddadapter(TCP) | 3 | 21 | 6 |
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
9K MPS BSF Profile
- Replication Factor: 1
- Message Size: 3500
- ACL FEED Type: ALL
Table 3-10 9K MPS BSF Profile
| Services | vCPU | Total Replica | Memory Required (Gi) | Topic Partitions |
|---|---|---|---|---|
| zookeeper | 1 | 3 | 1 | - |
| ocnaddkafka | 2 | 4 | 24 | - |
| ocnaddbsfaggregation | 2 | 1 | 2 | BSF=6 |
| MESSAGE SEQUENCING =ON and DD METADATA = ON/OFF | ||||
| ocnaddbsfaggregation | 2 | 1 | 16 | BSF=6 |
| ocnaddconsumeradapter(TCP FEED) | 3 | 1 | 4 | MAIN=6 |
| ocnaddconsumeradapter(HTT2 FEED) | 3 | 1 | 4 | MAIN=9 |
| FEED TYPE = CORRELATED_FILTERED (Minimum 20% data filter is configured) | ||||
| ocnaddfilter | 2 | 1 | 3 | MAIN=6,<feed-name>-FILTERED=6 |
| ocnaddcorrelation | 3 | 1 | 48 | <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=2and/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.4 Resource Profile for 135K MPS Message Sequencing and Metadata Enrichment
- Replication Factor: 2
- Message Size: 3500
- Feed Type: HTTP2/TCP/KAFKA
Table 3-11 Resource Requirement
| Service | vCPU | Total Replica | Memory Required (Gi) | Topic Partition |
|---|---|---|---|---|
| Kafka with RF=2 | ||||
| ocnaddkafka | 6 | 6 | 164 | - |
| MESSAGE_SEQUENCING_TYPE = TRANSACTION, TRANSACTION_MSG_SEQUENCING_EXPIRY_TIMER= 200ms and METADATA ENRICHMENT ON/OFF | ||||
| ocnaddscpaggregation | 2 | 5 | 24 | 30(SCP) |
| MESSAGE_SEQUENCING_TYPE = TIME_WINDOW, WINDOW_MSG_SEQUENCING_EXPIRY_TIMER=10ms | ||||
| ocnaddscpaggregation | 2 | 5 | 24 | 30(SCP) |
| MESSAGE_SEQUENCING_TYPE = REQUEST_RESPONSE, REQUEST_RESPONSE_MSG_SEQUENCING_EXPIRY_TIMER=10ms and METADATA ENRICHMENT ON/OFF | ||||
| ocnaddscpaggregation | 2 | 5 | 16 | 30(SCP) |
| INGRESS FILTER is ON | ||||
| MESSAGE_SEQUENCING_TYPE = TRANSACTION, TRANSACTION_MSG_SEQUENCING_EXPIRY_TIMER= 200ms and METADATA ENRICHMENT ON/OFF | ||||
| ocnaddscpaggregation | 2 | 6 | 36 | 36(SCP) |
| MESSAGE_SEQUENCING_TYPE = TIME_WINDOW, WINDOW_MSG_SEQUENCING_EXPIRY_TIMER=10ms | ||||
| ocnaddscpaggregation | 2 | 6 | 36 | 36(SCP) |
| MESSAGE_SEQUENCING_TYPE = REQUEST_RESPONSE, REQUEST_RESPONSE_MSG_SEQUENCING_EXPIRY_TIMER=10ms and METADATA ENRICHMENT ON/OFF | ||||
| ocnaddscpaggregation | 2 | 6 | 24 | 36(SCP) |
| HTTP2 Feed (FILTER = OFF) | ||||
| ocnaddadapter | 3 | 15 | 24 | 135(MAIN) |
| SYNTHETIC Feed (TCP CONNECTION MESSAGE and/or MESSAGE SEGEMENTATION = ON) (FILTER=OFF) | ||||
| ocnaddadapter | 3 | 11 | 12 | 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.5 Resource Profile for Aggregated Kafka Feed for 135K MPS
- Replication Factor: 1
- Message Size: 3500
- Feed Type: KAFKA
Table 3-12 Resource Requirement
| Service | 15K NRF Profile | 90K SCP Profile | 30K SEPP Profile | 135K Profile (SCP:90K NRF:15K SEPP:30K) | 135K SCP Profile | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| vCPU | Total Replica | Memory Required (Gi) | Topic Partitions | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | |
| zookeeper | 1 | 3 | 1 | 1 | 3 | 1 | 1 | 3 | 1 | 1 | 3 | 1 | 1 | 3 | 1 | |||||
| ocnaddkafka | 2 | 3 | 24 | 6 | 4 | 24 | 5 | 3 | 18 | 6.5 | 6 | 48 | 6.5 | 6 | 48 | |||||
| Replicated Feed | ||||||||||||||||||||
| ocnaddkafka | 2 | 3 | 24 | 7 | 4 | 48 | 6 | 3 | 24 | 7.5 | 6 | 96 | 7.5 | 6 | 96 | |||||
| Ingress FILTER is OFF | ||||||||||||||||||||
| ocnaddscpaggregation | - | - | - | - | 2 | 5 | 4 | SCP=30 | - | - | - | - | 2 | 5 | 4 |
SCP=30 (Each Instance 6 partition) |
2 | 8 | 4 |
SCP=48 (Each instance 6 partition) |
| ocnaddnrfaggregation | 2 | 1 | 2 | NRF=6 | - | - | - | - | - | - | - | - | 2 | 1 | 2 |
NRF=6 (Each Instance 6 partition) |
- | - | - | - |
| ocnaddseppaggregation | - | - | - | - | - | - | - | - | 2 | 2 | 4 | SEPP=12 | 2 | 2 | 4 |
SEPP=12 (Each Instance 6 partition) |
- | - | - | - |
| Ingress Filter is ON | ||||||||||||||||||||
| ocnaddscpaggregation | - | - | - | - | 2 | 6 | 4 | SCP=36 | - | - | - | - | 2 | 6 | 4 |
SCP=36 (Each Instance 6 partition) |
2 | 9 | 4 |
SCP=54 (Each instance 6 partition) |
| ocnaddnrfaggregation | 2 | 2 | 2 | NRF=12 | - | - | - | - | - | - | - | - | 2 | 2 | 2 |
NRF=12 (Each Instance 6 partition) |
- | - | - | - |
| ocnaddseppaggregation | - | - | - | - | - | - | - | - | 2 | 3 | 4 | SEPP=18 | 2 | 3 | 4 |
SEPP=18 (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.6 Resource Profile for Correlated Kafka Feed for 30K MPS
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
Table 3-13 Resource Requirement
| Service | 15K NRF Profile | 30K SCP Profile | 30K SEPP Profile | 30K Profile (SCP:15K NRF:5K SEPP:10K) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| vCPU | Total Replica | Memory Required (Gi) | Topic Partitions | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | |
| zookeeper | 1 | 3 | 1 | 1 | 3 | 1 | 1 | 3 | 1 | 1 | 3 | 1 | ||||
| ocnaddkafka | 3 | 4 | 24 | 4 | 4 | 24 | 4 | 4 | 24 | 4 | 4 | 24 | ||||
| EXPORT/TRACE(1K MPS rate is supported for inbound DD data) for 3 export configuration | ||||||||||||||||
| ocnaddexport | 3 | 1 | 24 | |||||||||||||
| Replicated Feed | ||||||||||||||||
| ocnaddkafka | 3 | 4 | 24 | 5 | 4 | 32 | 5 | 4 | 32 | 5 | 4 | 32 | ||||
| ocnaddscpaggregation | - | - | - | - | 2 | 2 | 2 | SCP=12 | - | - | - | - | 2 | 1 | 2 |
SCP=6 (Each Instance 6 partition) |
| ocnaddnrfaggregation | 2 | 1 | 2 | NRF=6 | - | - | - | - | - | - | - | - | 2 | 1 | 2 |
NRF=6 (Each Instance 6 partition) |
| ocnaddseppaggregation | - | - | - | - | - | - | - | - | 2 | 2 | 2 | SEPP=12 | 2 | 1 | 2 |
SEPP=6 (Each Instance 6 partition) |
| Feed TYPE = CORRELATED | ||||||||||||||||
| ocnaddcorrelation | 3 | 3 | 64 | MAIN=18,<feed-name>-CORRELATED=18 or as per consumer | 3 | 4 | 64 | MAIN=24,<feed-name>-CORRELATED=24 or as per consumer | 3 | 4 | 64 | MAIN=24,<feed-name>-CORRELATED=24 or as per consumer | 3 | 4 | 64 | MAIN=24,<feed-name>-CORRELATED=24 or as per consumer |
| Feed TYPE = CORRELATED_FILTERED (Minimum 20% data filter is configured) | ||||||||||||||||
| ocnaddfilter | 2 | 3 | 3 | MAIN=18,<feed-name>-FILTERED=18 | 2 | 4 | 3 | MAIN=24,<feed-name>-FILTERED=24 | 2 | 4 | 3 | MAIN=24,<feed-name>-FILTERED=24 | 2 | 4 | 3 | MAIN=24,<feed-name>-FILTERED=24 |
| ocnaddcorrelation | 3 | 3 | 48 | <feed-name>-FILTERED-CORRELATED=18 or as per consumer | 3 | 4 | 64 | <feed-name>-FILTERED-CORRELATED=24 or as per consumer | 3 | 4 | 64 | <feed-name>-FILTERED-CORRELATED=24 or as per consumer | 3 | 4 | 64 | <feed-name>-FILTERED-CORRELATED=24 or as per consumer |
| Per Correlation Feed(1K MPS supported with 24 hours retention) | ||||||||||||||||
| storageadapter | 3 | 1 | 16 | |||||||||||||
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.7 Resource Profile for Non-Oracle Network Function Feed for 5K MPS
- Replication Factor: 1
- Message Size: 3500
- Feed Type: Non-Oracle Network Function Feed
Table 3-14 Resource Requirement
| Service | 5K NON ORACLE NF Profile | |||
|---|---|---|---|---|
| vCPU | Total Replica | Memory Required (Gi) | Topic Partitions | |
| ocnaddingressadapter | 3 | 1 | 8 | |
| zookeeper | 1 | 3 | 1 | |
| ocnaddnonoracleaggregation | 2 | 1 | 2 | NON_ORACLE=6 |
| ocnaddkafka | 2 | 3 | 16 | |
| ocnaddadapter | 3 | 1 | 6 | MAIN=9 |
| Replicated Feed | ||||
| ocnaddkafka | 2 | 3 | 24 | |
| ocnaddadapter | 3 | 2 | 6 | MAIN=18 |
3.1.3.8 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-15 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 |
| ocnaddadapter | 3 | 3 | 6 | 6 |
HTTP2: 2 SYNTHETIC: 1 |
HTTP2: 13 SYNTHETIC: 9 |
117 | MAIN |
| ocnaddkafka | 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.4 Resource Profile for OCI Environment
This section displays the profile resource requirements in OCI environment.
3.1.4.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
Table 3-16 Resource Requirement
| Service | 5K Profile (SCP:3K NRF:1K SEPP:1K) | 5K SCP Profile | ||||||
|---|---|---|---|---|---|---|---|---|
| vCPU | Total Replica | Memory Required (Gi) | Topic Partition | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | |
| 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 | ||
| ocnaddgui | 2 | 1 | 1 | 2 | 1 | 1 | ||
| ocnadduirouter | 2 | 1 | 1 | 2 | 1 | 1 | ||
| zookeeper | 1 | 3 | 1 | 1 | 3 | 1 | ||
| ocnaddkafka | 2 | 4 | 24 | 2 | 4 | 24 | ||
| Replicated Feed (Avg Latency: 1ms) | ||||||||
| ocnaddkafka | 3 | 4 | 32 | 3 | 4 | 32 | ||
| Single Feed (Avg Latency: 1ms) | ||||||||
| ocnaddscpaggregation | 2 | 1 | 2 |
SCP=6 (Each Instance 6 partition) |
2 | 2 | 2 |
SCP=12 (Each instance 6 partition) |
| ocnaddnrfaggregation | 2 | 1 | 2 |
NRF=6 (Each Instance 6 partition) |
- | - | - | - |
| ocnaddseppaggregation | 2 | 1 | 2 |
SEPP=12 (Each Instance 6 partition) |
- | - | - | - |
| ocnaddadapter | 3 | 2 | 3 |
MAIN=18 (Each instance 9 partition) |
3 | 2 | 3 |
MAIN=18 (Each instance 9 partition) |
3.1.4.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
Table 3-17 Resource Requirement
| Service | 5K Profile (SCP:3K NRF:1K SEPP:1K) | 5K SCP Profile | ||||||
|---|---|---|---|---|---|---|---|---|
| vCPU | Total Replica | Memory Required (Gi) | Topic Partition | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | |
| 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 | ||
| ocnaddgui | 2 | 1 | 1 | 2 | 1 | 1 | ||
| ocnadduirouter | 2 | 1 | 1 | 2 | 1 | 1 | ||
| zookeeper | 1 | 3 | 1 | 1 | 3 | 1 | ||
| ocnaddkafka | 2 | 4 | 24 | 2 | 4 | 24 | ||
| Replicated Feed | ||||||||
| ocnaddkafka | 3 | 4 | 32 | 3 | 4 | 32 | ||
| Single Feed | ||||||||
| ocnaddscpaggregation | 2 | 1 | 2 |
SCP=6 (Each Instance 6 partition) |
2 | 2 | 2 |
SCP=12 (Each instance 6 partition) |
| ocnaddnrfaggregation | 2 | 1 | 2 |
NRF=6 (Each Instance 6 partition) |
- | - | - | - |
| ocnaddseppaggregation | 2 | 1 | 2 |
SEPP=12 (Each Instance 6 partition) |
- | - | - | - |
3.1.4.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
Table 3-18 Resource Requirement
| Service | 5K Profile (SCP:3K NRF:1K SEPP:1K) | 5K SCP Profile | ||||||
|---|---|---|---|---|---|---|---|---|
| vCPU | Total Replica | Memory Required (Gi) | Topic Partition | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | |
| 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 | ||
| ocnaddgui | 2 | 1 | 1 | 2 | 1 | 1 | ||
| ocnadduirouter | 2 | 1 | 1 | 2 | 1 | 1 | ||
| zookeeper | 1 | 3 | 1 | 1 | 3 | 1 | ||
| ocnaddkafka | 3 | 4 | 24 | 3 | 4 | 24 | ||
| Replicated Feed (Avg Latency: 0.3ms) | ||||||||
| ocnaddkafka | 4 | 4 | 32 | 4 | 4 | 32 | ||
| Single Feed (Avg Latency: 0.3ms) | ||||||||
| ocnaddscpaggregation | 2 | 1 | 2 |
SCP=6 (Each Instance 6 partition) |
2 | 2 | 2 |
SCP=12 (Each instance 6 partition) |
| ocnaddnrfaggregation | 2 | 1 | 2 |
NRF=6 (Each Instance 6 partition) |
- | - | - | - |
| ocnaddseppaggregation | 2 | 1 | 2 |
SEPP=12 (Each Instance 6 partition) |
- | - | - | - |
| ocnaddadapter | 3 | 2 | 3 |
MAIN=12 (Each instance 6 partition) |
3 | 2 | 3 |
MAIN=12 (Each instance 6 partition) |
3.1.4.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
Table 3-19 Resource Requirement
| Service | 5K SCP Profile | 5K Profile (SCP:3K NRF:1K SEPP:1K) | ||||||
|---|---|---|---|---|---|---|---|---|
| vCPU | Total Replica | Memory Required (Gi) | Topic Partition | vCPU | Total Replica | Memory Required (Gi) | Topic Partition | |
| 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 | ||
| ocnaddgui | 2 | 1 | 1 | 2 | 1 | 1 | ||
| ocnadduirouter | 2 | 1 | 1 | 2 | 1 | 1 | ||
| zookeeper | 1 | 3 | 1 | 1 | 3 | 2 | ||
| ocnaddkafka | 3 | 4 | 32 | 3 | 4 | 32 | ||
| Feed TYPE = CORRELATED | ||||||||
| ocnaddscpaggregation | 2 | 1 | 2 |
SCP=6 (Each Instance 6 partition) |
2 | 2 | 2 |
SCP=12 (Each instance 6 partition) |
| ocnaddnrfaggregation | 2 | 1 | 2 |
NRF=6 (Each Instance 6 partition) |
- | - | - | - |
| ocnaddseppaggregation | 2 | 1 | 2 |
SEPP=12 (Each Instance 6 partition) |
- | - | - | - |
| ocnaddcorrelation | 3 | 3 | 24 | MAIN=18,<feed-name>-CORRELATED=18 or as per consumer | 3 | 3 | 24 | 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 | 2 | 3 | 3 | MAIN=18,<feed-name>-FILTERED=18 |
| ocnaddcorrelation | 2 | 3 | 16 | <feed-name>-FILTERED-CORRELATED=18 or as per consumer | 2 | 3 | 16 | <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
The ocnaddkafka and Zookeeper services use the POD anti-affinity rules. The rules are intended to support even distribution of Kafka and Zookeeper pods across the available nodes.
Zookeeper Service Anti-affinity Rules
Zookeeper service anti-affinity rules are listed below:
spec:
affinity:
podAntiAffinity:
preferredDuringSchedulingIgnoredDuringExecution:
- weight: 100
podAffinityTerm:
labelSelector:
matchExpressions:
- key: app
operator: In
values:
- zookeeper
topologyKey: topology.kubernetes.io/zoneocnaddkafka Service Anti-affinity Rules
ocnaddkafka service anti-affinity rules are listed below:
spec:
topologySpreadConstraints:
- maxSkew: 1
topologyKey: kubernetes.io/hostname
whenUnsatisfiable: ScheduleAnyway
labelSelector:
matchLabels:
app1 : nodeselectionThe configuration ensures the scheduler keeps equal number of pods matching the constraint on every node. However, the parameter whenUnsatisfiable set to ScheduleAnyway, helps to schedule the pod, but the scheduler prioritizes honoring the skew to not make the cluster more imbalanced.
3.3 Ephemeral Storage Requirements
The following table describes the Ephemeral Storage requirements for OCNADD:
Table:Ephemeral Storage
Table 3-20 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 | 1000 | 1000 | - |
| ocnaddscpaggregation | 100 | 500 | - |
| ocnaddseppaggregation | 100 | 500 | - |
| ocnaddnrfaggregation | 100 | 500 | - |
| ocnaddbsfaggregation | 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
Table 3-21 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 listof original5G 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.
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 -1Average 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)
Table 3-22 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 (in Bytes) | Rate | Avg Size (in Bytes) | Rate | Avg Size (in 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 listof original5G 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-23 Retention Period Per Topic
| Topic Name | Retention Period |
|---|---|
| SCP | 5 Minutes |
| NRF | 5 Minutes |
| SEPP | 5 Minutes |
| MAIN | 6 Hours (Max) |
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 SizeWhere,
MPS is "Message Per Second"
RF is "Replication Factor"
- Average Message Size = 1941 Bytes
The following example uses the values from the first row of the Table 3-22 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] - Average Message Size = 3769 Bytes
The following example uses the values from the fourth row of the Table 3-22 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]