3.1 Profile Resource Requirements
Note:
For information on increasing partitions in Kafka topics see, "Adding Partitions to an Existing Topic" section in Oracle Communications Network Analytics Data Director User Guide.The following table displays the profile resource requirements when HTTP2 FEED is "65K" and WEIGHTED_LB is "OFF":
Table 3-3 Resource Requirements
| OCNADD Service | 9K NRF Profile | 41K SCP Profile | 15K SEPP Profile | 65K Profile (SCP:41K NRF:9K SEPP:15K) | 65K SCP Profile | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Replication Factor = 1 Message Size = 3500 FEED Type = HTTP2 |
vCPU | Total Replica |
Memory Required (Gi) |
Topic Partitions | vCPU | Total Replica |
Memory Required (Gi) |
Topic Partitions | vCPU | Total Replica |
Memory Required (Gi) |
Topic Partitions | vCPU | Total Replica |
Memory Required (Gi) |
Topic Partitions | vCPU | Total Replica |
Memory Required (Gi) |
Topic Partitions |
| ocnaddconfiguration | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||
| ocnaddalarm | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||
| ocnaddadmin | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||
| ocnaddhealthmonitoring | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||
| ocnaddscpaggregation | 2 | 2 | 2 | SCP=12 | 2 | 2 | 2 |
SCP=12 (6 partitions in each instance) |
2 | 2 | 2 |
SCP=12 (6 partitions in each instance) |
||||||||
| ocnaddnrfaggregation | 2 | 1 | 2 | NRF=6 | 2 | 1 | 2 |
NRF=6 (6 partitions in each instance) |
||||||||||||
| ocnaddseppaggregation | 2 | 1 | 2 | SEPP=6 | 2 | 1 | 2 |
SEPP=6 (6 partitions in each instance) |
||||||||||||
| ocnaddadapter | 3 | 2 | 3 | MAIN=18 | 3 | 4 | 3 | MAIN=36 | 3 | 2 | 3 | MAIN=18 | 3 | 8 | 4 |
MAIN=72 (9 partitions in each instance) |
3 | 8 | 4 |
MAIN=72 (9 partitions in each instance) |
| ocnaddkafka | 2 | 3 | 12 | 3 | 3 | 24 | 3 | 3 | 12 | 5 | 3 | 48 | 5 | 3 | 48 | |||||
| zookeeper | 1 | 3 | 1 | 1 | 3 | 1 | 1 | 3 | 1 | 1 | 3 | 2 | 1 | 3 | 2 | |||||
| ocnaddgui | 2 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | 1 | |||||
| ocnadduirouter | 2 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | 1 | |||||
| ocnaddcache | 1 | 2 | 10 | 1 | 2 | 10 | 1 | 2 | 10 | 1 | 2 | 10 | 1 | 2 | 10 | |||||
Note:
- Four 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
The following table displays the profile resource requirements when HTTP2 FEED is "65K" and WEIGHTED_LB is "ON", and/or Filter is "ON":
Note:
For more information on weighted load balancing, see Oracle Communications Network Analytics Data Director User Guide and Oracle Communications Network Analytics Data Director Installation, Upgrade, and Fault Recovery Guide.Note:
If ADAPTER_CORRID_LB_WITHOUT_LF_ENABLED is "True", the resource requirements in Table 3-3 table are applicable. If ADAPTER_CORRID_LB_WITHOUT_LF_ENABLED is "False", see the resource requirements in the following table. Resources are updated only for the ocnaddadapter and ocnaddcache services. See the Table 3-3 table for all other service configurations.Table 3-4 Resource Requirements
| OCNADD Service | 9K NRF Profile | 41K SCP Profile | 15K SEPP Profile | 65K Profile or 65K SCP Profile (SCP:41K NRF:9K SEPP:15K) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Replication Factor = 1 Message Size = 3500 FEED Type = HTTP2 |
vCPU | Total Replica |
Memory Required (Gi) |
Topic Partitions | vCPU | Total Replica |
Memory Required (Gi) |
Topic Partitions | vCPU | Total Replica |
Memory Required (Gi) |
Topic Partitions | vCPU | Total Replica |
Memory Required (Gi) |
Topic Partitions |
| ocnaddadapter | 3 | 3 | 3 | MAIN=27 | 3 | 7 | 3 | MAIN=63 | 3 | 3 | 3 | MAIN=27 | 3 | 13 | 4 |
MAIN=117 (Each instance 9 partition) |
| ocnaddcache | 1 | 3 | 24 | 1 | 4 | 24 | 1 | 3 | 24 | 1 | 6 | 30 | ||||
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.
- Four 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.
The following table displays the profile resource requirements when SYNTHETIC FEED is "30K" and WEIGHTED_LB is "OFF":
Table 3-5 Resource Requirements
| OCNADD Service | 6K NRF Profile | 15K SCP Profile | 9K SEPP Profile | 30K Profile (SCP:15K NRF:6K SEPP:9K) | 30K SCP Profile | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Replication Factor = 1 Message Size = 3500 FEED Type = SYNTHETIC |
vCPU | Total Replica |
Memory Required (Gi) |
Topic Partitions | vCPU | Total Replica |
Memory Required (Gi) |
Topic Partitions | vCPU | Total Replica |
Memory Required (Gi) |
Topic Partitions | vCPU | Total Replica |
Memory Required (Gi) |
Topic Partitions | vCPU | Total Replica |
Memory Required (Gi) |
Topic Partitions |
| ocnaddconfiguration | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||
| ocnaddalarm | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||
| ocnaddadmin | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||
| ocnaddhealthmonitoring | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||
| ocnaddscpaggregation | 2 | 1 | 2 | SCP=6 | 2 | 1 | 2 |
SCP=6 (Each instance 6 partitions) |
2 | 1 | 2 |
SCP=6 (Each instance 6 partitions) |
||||||||
| ocnaddnrfaggregation | 2 | 1 | 2 | NRF=6 | 2 | 1 | 2 |
NRF=6 (Each instance 6 partitions) |
||||||||||||
| ocnaddseppaggregation | 2 | 1 | 2 | SEPP=6 | 2 | 1 | 2 |
SEPP=6 (Each instance 6 partitions) |
||||||||||||
| ocnaddadapter | 3 | 1 | 3 | MAIN=6 | 3 | 1 | 3 | MAIN=6 | 3 | 1 | 3 | MAIN=6 | 3 | 2 | 4 |
MAIN=12 (Each instance 6 partitions) |
3 | 2 | 4 |
MAIN=12 (Each instance 6 partitions) |
| ocnaddkafka | 2 | 3 | 12 | 3 | 3 | 24 | 3 | 3 | 12 | 5 | 3 | 48 | 5 | 3 | 48 | |||||
| zookeeper | 1 | 3 | 1 | 1 | 3 | 1 | 1 | 3 | 1 | 1 | 3 | 2 | 1 | 3 | 2 | |||||
| ocnaddgui | 2 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | 1 | |||||
| ocnadduirouter | 2 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | 1 | |||||
| ocnaddcache | 1 | 2 | 10 | 1 | 2 | 10 | 1 | 2 | 10 | 1 | 2 | 10 | 1 | 2 | 10 | |||||
Note:
- Four 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.
The following table displays the profile resource requirements when SYNTHETIC FEED is "30K" and WEIGHTED_LB is "ON", and/or Filter is "ON":
Note:
For more information on weighted load balancing see, Oracle Communications Network Analytics Data Director User Guide and Oracle Communications Network Analytics Data Director Installation, Upgrade, and Fault Recovery Guide.Note:
If ADAPTER_CORRID_LB_WITHOUT_LF_ENABLED is "True", the resource requirements in the Table 3-5 table are applicable. If ADAPTER_CORRID_LB_WITHOUT_LF_ENABLED is "False", see the resource requirements in the following table. Resources are updated only for the ocnaddadapter and ocnaddcache services, see the Table 3-5 table for all other service configurations.Table 3-6 Resource Requirements
| OCNADD Service | 6K NRF Profile | 15K SCP Profile | 9K SEPP Profile | 30K Profile or 30K SCP Profile (SCP:15K NRF:9K SEPP:6K) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Replication Factor = 1 Message Size = 3500 FEED Type = HTTP2, SYNTHETIC |
vCPU | Total Replica |
Memory Required (Gi) |
Topic Partitions | vCPU | Total Replica |
Memory Required (Gi) |
Topic Partitions | vCPU | Total Replica |
Memory Required (Gi) |
Topic Partitions | vCPU | Total Replica |
Memory Required (Gi) |
Topic Partitions |
| ocnaddadapter | 3 | 1 | 3 | MAIN=6 | 3 | 2 | 3 | MAIN=12 | 3 | 1 | 3 | MAIN=6 | 3 | 4 | 4 |
MAIN=24 (Each instance 6 partitions) |
| ocnaddcache | 1 | 3 | 24 | 1 | 4 | 24 | 1 | 3 | 24 | 1 | 6 | 24 | ||||
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.
- Four 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.