4 OCNADD Benchmarking Testing

This section describes the performance testing scenarios and results for the Message Feed functionality provided by Oracle Communications Network Analytics Data Director. The message feed feature is tested with SCP, NRF, and SEPP as the source of the message feed.

4.1 Performance Benchmarking with Synthetic Feed with Replication

The performance benchmarking test is performed on OCNADD with 110K MPS traffic (feed replication enabled) which includes 65K MPS SCP traffic (32.5K TPS with 2 traffic copy trigger points on SCP), 15K MPS NRF traffic (7.5K TPS with 2 traffic copy trigger points on NRF) and 30K MPS SEPP traffic (15K TPS with 2 traffic copy trigger points on SEPP). The benchmarking results are provided below:

Note:

One Ingress message from a NF is "1" MPS for OCNADD.

Benchmark Test Environment

The test environment specifications are listed below:
  • Ingress Traffic Rate: 110K MPS
  • The latency, resource utilization, and MPS is observed for the period of 3 hrs or more.
  • OCNADD single site deployment with ASM disabled
  • OCNADD Release 24.1.0 deployed over CNE (Bare metal) 23.3.4 version
  • Kafka Replication Factor (RF): 1
  • OCNADD TCP Feed: TCP/TLS
  • OCNADD Kafka PVC: 400GB

    For more information about PVC requirements, see Kafka PVC Storage Requirements.

  • 3rd Party Application: With 2 End-points
  • cnDBTier Release 24.1.0
  • NRF Release 24.1.0
  • SCP Release 24.1.0
  • SEPP Release 24.1.0
  • SASL/SSL, enabled between NRF/SCP/SEPP and OCNADD
  • CNCC Release 24.1.0
  • Message Size: 3450 Bytes
  • Environment: CNE (Bare metal), "3" Master Nodes (X9 Server and NVME), "3" Worker Nodes (X9 Server and NVME).
  • Execution time: 12 Hours
  • NRF: IGW and EGW messageCopy feature is enabled
  • SCP: Default configuration
  • cSEPP: PLMN IGW messageCopy feature is enabled
  • pSEPP: The messageCopy feature is disabled

Benchmark Testcase Specifications

The testcase parameters are as follows:
  • OCNADD
    • A feed is configured using the OCNADD Console with aggregation rules set for SCP, NRF and SEPP.
    • Message Ingestion Rate: 110K MPS
    Resource Specifications:

    Table 4-1 OCNADD Resource Specifications

    Services CPU Request Per Pod CPU Limit Per Pod Memory Request Per Pod (Gi) Memory Limit Per Pod (Gi) min Replicas max Replicas Kafka Topic Partitions and Retention
    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 -
    ocnadduirouter 2 2 1 1 1 1 -
    ocnaddscpaggregation 2 2 4 4 2 2

    24 (SCP)/

    retention.ms = 300000
    ocnaddnrfaggregation 2 2 2 2 1 1

    6 (NRF)/

    retention.ms = 300000
    ocnaddseppaggregation 2 2 4 4 2 2

    12 (SEPP)/

    retention.ms = 300000
    ocnaddadapter 3 3 6 6 9 9

    54 (MAIN)/

    retention.ms = 300000
    ocnaddkafka 7 7 96 96 6 6 -
    zookeeper 1 1 2 2 3 3 -
    ocnaddgui 2 2 1 1 1 1 -
  • SCP

    SCP Traffic: 65K TPS using two trigger points.

  • NRF

    NRF Traffic: 15K TPS using two trigger points.

  • SEPP

    SEPP Traffic: 30K TPS using two trigger points.

Benchmark Test Results

Traffic Feed Details

Table 4-2 Traffic Feed Details

NF NF Traffic Copy Trigger Points Traffic Rate Duration in hours E2E Traffic Feed Average Latency E2E Traffic Feed Success Rate
OCNADD NA 110K MPS 12

Feed-1: 15.5 msec

Feed-2: 14.4 msec

Feed-1: 99.94%

Feed-2: 99.96%
NRF 2 - IGW/EGW (Request and Response) 15K MPS 12 NA 99.94%
SCP 2 (Request Ingress/Request Egress) 65K MPS 12 NA 99.97%
SEPP 2 (PLMN IGW) (Request and Response) 30K MPS 12 NA 99.93%

CPU and Memory Utilization

The following table describes the OCNADD CPU and memory utilization:

Table 4-3 OCNADD CPU and Memory Utilization

Microservice/ Container Pod Count CPU Utilization (%) Memory Utilization (%)
ocnaddadminservice 1 0.09% 28.80%
ocnaddalarm 1 0.08% 18.10%
ocnaddconfiguration 1 0.09% 36.60%
ocnaddgui 1 0.00% 1.79%
ocnaddhealthmonitoring 1 0.17% 33.90%
ocnadduirouter 1 0.01% 29.10%
ocnaddfilter 1 48.70% 12.70%
ocnaddnrfaggregation 1 82.80% 34.00%
ocnaddscpaggregation 4 74.50% 23.10%
ocnaddseppaggregation 2 72.40% 21.00%
feed-dd11-adapter 9 84.80% 24.30%
kafka-broker 6 72.20% 18.40%
zookeeper 3 0.13% 21.80%
feed-dd22-adapter 9 83.30% 23.70%

4.2 Performance Benchmarking with Correlated Feed for XDR Generation

The performance benchmarking test is performed on OCNADD with correlated feed for XDR generation in a centralized deployment. The traffic includes 20K MPS SCP traffic (10K TPS with 2 traffic copy trigger points on SCP), 4K MPS NRF traffic (2K TPS with 2 traffic copy trigger points on NRF), and 6K MPS SEPP traffic (3K TPS with 2 traffic copy trigger points on SEPP). The benchmarking results are provided below:

Note:

One Ingress message from a NF is "1" MPS for OCNADD.

Benchmark Test Environment

The test environment specifications are listed below:
  • Ingress Traffic Rate: 100K MPS
  • The latency, resource utilization, and MPS is observed for the period of 3 hrs or more.
  • OCNADD single site deployment with ASM disabled
  • OCNADD Release 23.4.0 deployed over CNE (Bare metal) 22.3.0 version
  • Kafka Replication Factor (RF): 1
  • OCNADD Correlated Feed: HTTP2/TLS
  • OCNADD Kafka PVC: 400GB

    For more information about PVC requirements, see Kafka PVC Storage Requirements.

  • 3rd Party Application: With 2 End-points
  • cnDBTier Release 23.4.0
  • NRF Release 23.4.0
  • SCP Release 23.3.0
  • SEPP Release 23.4.0
  • SASL/SSL, enabled between NRF/SCP/SEPP and OCNADD
  • CNCC Release 23.4.0
  • Message Size: 3300 bytes
  • Environment: CNE (Bare metal)
  • Execution time: 12 Hours
  • NRF: IGW and EGW messageCopy feature is enabled
  • SCP: Default configuration
  • cSEPP: PLMN IGW messageCopy feature is enabled
  • pSEPP: The messageCopy feature is disabled

Benchmark Testcase Specifications

The testcase parameters are as follows:
  • OCNADD
    • A feed is configured using the OCNADD Console with aggregation rules set for SCP, NRF and SEPP.
    • Message Ingestion Rate: 100K MPS
    Resource Specifications:

    Table 4-4 OCNADD Resource Specifications

    Services CPU Request Per Pod CPU Limit Per Pod Memory Request Per Pod (Gi) Memory Limit Per Pod (Gi) min Replicas max Replicas Kafka Topic Partitions and Retention
    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 -
    ocnadduirouter 2 2 1 1 1 1 -
    ocnaddscpaggregation 2 2 2 2 2 2

    18 (SCP)/

    retention.ms = 300000
    ocnaddnrfaggregation 2 2 2 2 1 1

    6 (NRF)/

    retention.ms = 300000
    ocnaddseppaggregation 2 2 2 2 2 2

    12 (SEPP)/

    retention.ms = 300000
    ocnaddadapter 3 3 4 4 9 9

    54 (MAIN)/

    retention.ms = 300000
    ocnaddkafka 8 8 64 64 4 4 -
    zookeeper 1 1 2 2 3 3 -
    ocnaddgui 2 2 1 1 1 1 -
  • SCP

    SCP Traffic: 20K TPS using two trigger points.

  • NRF

    NRF Traffic: 4K TPS using two trigger points.

  • SEPP

    SEPP Traffic: 6K TPS using two trigger points.

Benchmark Test Results

Traffic Feed Details

Table 4-5 Traffic Feed Details

NF NF Traffic Copy Trigger Points Traffic Rate Duration in hours E2E Traffic Feed Average Latency E2E Traffic Feed Success Rate
OCNADD NA 30K MPS 12 NA

99.99%
NRF 2 - IGW/EGW (Request and Response) 4K MPS 12 NA 99.99%
SCP 2 (Request Ingress/Request Egress) 20K MPS 12 NA 99.99%
SEPP 2 (PLMN IGW) (Request and Response) 6K MPS 12 NA 99.99%

CPU and Memory Utilization

The following table describes the OCNADD CPU and memory utilization:

Table 4-6 OCNADD CPU and Memory Utilization

Microservice/ Container Pod Count CPU Utilization (%) Memory Utilization (%)
ocnaddadminservice 1 0.13% 29.40%
ocnaddalarm 1 0.34% 21.80%
ocnaddconfiguration 1 0.14% 34.80%
ocnaddgui 1 0.00% 5.09%
ocnaddhealthmonitoring 1 0.29% 35.30%
ocnadduirouter 1 0.06% 29.20%
kafka-broker 4 52.10% 35.90%
zookeeper 4 0.14% 18.10%
ocnaddfilter 4 49.50% 15.40%
ocnaddnrfaggregation 1 63.60% 55.50%
ocnaddscpaggregation 3 49.20% 46.60%
ocnaddseppaggregation 2 39.00% 39.10%
feed-dd1-correlation 16 23.40% 26.50%

4.3 Performance Benchmarking with Synthetic Feed with Replication in OCI Environment

The performance benchmarking test is performed on OCNADD with 5K MPS traffic, which includes 3K MPS SCP traffic, 1K MPS NRF traffic, and 1K MPS SEPP traffic, in a centralized deployment with one worker group. The benchmarking results are provided below:

Note:

An ingress message from a NF is '1' MPS for OCNADD.

Benchmark Test Environment

The test environment specifications are listed below:
  • Ingress Traffic Rate: 5K MPS
  • The latency, resource utilization, and MPS is observed for the period of 3 hrs or more.
  • OCNADD single site deployment with ASM disabled
  • OCNADD Release 24.1.0 deployed over OCI.
  • Kafka Replication Factor (RF): 1
  • OCNADD TCP Feed: TCP/TLS
  • OCNADD Kafka PVC: 50GB
  • 3rd Party Application: OCNADD Simulator with one endpoint
  • cnDBTier Release 24.1.0
  • NRF Release: NA
  • SCP Release: NA
  • SEPP Release: NA
  • SASL/SSL, enabled between OCNADD Simulator and OCNADD
  • CNCC Release 24.1.0
  • Message Size: 3330 Bytes
  • Environment: OCI environment, "6" Worker Nodes, "VM.Standard.E4.Flex" Instance Shape, "194 GB" memory in Worker Node, "50 (CPU: 100)" OCPUs in the Worker Nodes
  • Execution time: 16 Hours

Benchmark Testcase Specifications

The testcase parameters are as follows:
  • OCNADD
    • Message Ingestion Rate: 5K MPS
    Resource Specifications:

    Table 4-7 OCNADD Worker Group Resource Specifications

    Services CPU Request Per Pod CPU Limit Per Pod Memory Request Per Pod (Gi) Memory Limit Per Pod (Gi) min Replicas max Replicas Kafka Topic Partitions and Retention
    ocnaddconfiguration 1 1 2 2 1 1 -
    ocnaddalarm 1 1 2 2 1 1 -
    ocnaddadmin 1 1 2 2 1 1 -
    ocnaddhealthmonitoring 1 1 2 2 1 1 -
    ocnadduirouter 0 0 0 0 0 0 -
    ocnaddscpaggregation 2 2 4 4 1 1

    6 (SCP)/

    retention.ms = 300000
    ocnaddnrfaggregation 2 2 4 4 1 1

    6 (NRF)/

    retention.ms = 300000
    ocnaddseppaggregation 2 2 4 4 1 1

    12 (SEPP)/

    retention.ms = 300000
    ocnaddadapter 3 3 5 5 2 2

    12 (MAIN)/

    retention.ms = 300000
    ocnaddkafka 4 4 32 32 4 4 -
    zookeeper 1 1 3 3 3 3 -
    ocnaddgui 0 0 0 0 0 0 -
  • SCP

    SCP Traffic: 3K TPS in a centralized deployment having one worker group.

  • NRF

    NRF Traffic: 1K TPS in a centralized deployment having one worker group.

  • SEPP

    SEPP Traffic: 1K TPS in a centralized deployment having one worker group.

Benchmark Test Results

Traffic Feed Details

Table 4-8 Traffic Feed Details

NF NF Traffic Copy Trigger Points Traffic Rate Duration in hours E2E Traffic Feed Average Latency E2E Traffic Feed Success Rate
OCNADD Worker Group NA 5K MPS 16

Feed-1: 5 msec

Feed-2: 4 msec

99.99%
NRF 2 - IGW/EGW (Request and Response) 1K MPS 16 NA NA
SCP 2 (Request Ingress/Request Egress) 3K MPS 16 NA NA
SEPP 2 (PLMN IGW) (Request and Response) 1K MPS 16 NA NA

CPU and Memory Utilization

The following table describes the OCNADD CPU and memory utilization:

Table 4-9 OCNADD CPU and Memory Utilization

Microservice/ Container Pod Count CPU Utilization (%) Memory Utilization (%)
ocnaddadminservice 1 54.764% 53.423%
ocnaddalarm 1 0.205% 60.424%
ocnaddconfiguration 1 0.214% 64.145%
ocnaddhealthmonitoring 1 0.275% 54.615%
kafka-broker 4 74.323% 59.958%
zookeeper 3 0.430052465% 53.955%
ocnaddnrfaggregation 1 40.833% 78.980%
ocnaddscpaggregation 1 60.754% 82.635%
ocnaddseppaggregation 1 44.205% 84.717%

4.4 Performance Benchmarking with 60K MPS SEPP Traffic with HTTP2 Feed Replication

The performance benchmarking test is performed on OCNADD with SEPP HTTP2 feed (replication enabled) in a centralized deployment with one worker group. The traffic includes 60K MPS SEPP traffic (15K TPS with 4 traffic copy trigger points on SEPP). The benchmarking results are provided below:

Note:

One Ingress message from a NF is "1" MPS for OCNADD.

Benchmark Test Environment

The test environment specifications are listed below:
  • Ingress Traffic Rate: 60K MPS
  • The latency, resource utilization, and MPS is observed for the period of 3 hrs or more.
  • OCNADD single site deployment with ASM disabled
  • OCNADD Release 24.2.0 deployed over CNE (Bare metal) 23.3.4 version
  • Kafka Replication Factor (RF): 1
  • OCNADD Data Feed: HTTP2/TLS
  • OCNADD Kafka PVC: 400GB

    For more information about PVC requirements, see Kafka PVC Storage Requirements.

  • 3rd Party Application: With 2 End-points
  • cnDBTier Release 24.2.0
  • SEPP Release 24.2.0
  • SASL/SSL, enabled between NRF, SCP, SEPP and OCNADD
  • CNCC Release 24.2.0
  • Message Size: 3550 bytes
  • Environment: CNE (Bare metal)
  • Execution time: 12 Hours
  • cSEPP: PLMN IGW and N32 EGW messageCopy feature enabled
  • pSEPP: The messageCopy feature is disabled

Benchmark Testcase Specifications

The testcase parameters are as follows:
  • OCNADD
    • A feed is configured using the OCNADD Console with aggregation rules set for SCP, NRF and SEPP.
    • Message Ingestion Rate: 60K MPS
    Resource Specifications:

    Table 4-10 OCNADD Resource Specifications

    Services CPU Request Per Pod CPU Limit Per Pod Memory Request Per Pod (Gi) Memory Limit Per Pod (Gi) min Replicas max Replicas Kafka Topic Partitions and Retention
    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 -
    ocnadduirouter 2 2 1 1 1 1 -
    ocnaddscpaggregation 2 2 2 2 4 4

    6 (SCP)/

    retention.ms = 300000
    ocnaddnrfaggregation 2 2 2 2 1 1

    6 (NRF)/

    retention.ms = 300000
    ocnaddseppaggregation 2 2 2 2 5 5

    24 (SEPP)/

    retention.ms = 300000
    ocnaddadapter 3 3 24 24 15 15

    126 (MAIN)/

    retention.ms = 300000
    ocnaddkafka 7.5 7.5 96 96 6 6 -
    zookeeper 1 1 2 2 3 3 -
    ocnaddgui 2 2 1 1 1 1 -
  • SEPP

    SEPP Traffic: 60K TPS using four trigger points.

Benchmark Test Results

Traffic Feed Details

Table 4-11 Traffic Feed Details

NF NF Traffic Copy Trigger Points Traffic Rate Duration in hours E2E Traffic Feed Average Latency E2E Traffic Feed Success Rate
OCNADD NA 60K MPS 12

Feed-1: 2.42 msec

Feed-2: 2.42 sec

Feed-1: 99.97%

Feed-2: 99.96%
SEPP 2 (PLMN IGW) (Request and Response)

2 - N32 EGW (Request and Response)

 60K MPS 12 NA 99.99%

CPU and Memory Utilization

The following table describes the OCNADD CPU and memory utilization:

Table 4-12 OCNADD CPU and Memory Utilization

Micro-Service/ Container Pod Count CPU Utilization (%) Memory Utilization (%)
ocnaddfilter 1 0.07% 15.60%
ocnaddnrfaggregation 1 0.06% 18.30%
ocnaddscpaggregation 1 0.06% 10.20%
ocnaddseppaggregation 5 80.10% 35.60%
feed-dd1-adapter 15 41.70% 20.50%
kafka-broker 6 62.10% 10.70%
zookeeper 3 0.15% 18.20%
feed-dd2-adapter 15 41.90% 17.20%
ocnaddadminservice 1 0.12% 27.80%
ocnaddalarm 1 0.14% 18.60%
ocnaddconfiguration 1 0.15% 38.70%
ocnaddexport 1 0.02% 2.03%
ocnaddgui 1 0.00% 2.23%
ocnaddhealthmonitoring 1 0.27% 38.20%
ocnadduirouter 1 0.01% 31.00%

4.5 Performance Benchmarking with 135K MPS Traffic and HTTP2 Feed Replication

The performance benchmarking test is performed on OCNADD with 135K MPS traffic and feed replication enabled. The traffic includes:
  • SCP Traffic: 90K MPS (32.5K TPS with 2 trigger points)
  • NRF Traffic: 15K MPS (7.5K TPS with 2 trigger points)
  • SEPP Traffic: 30K MPS (15K TPS with 2 trigger points)

The benchmarking results are provided below:

Note:

One Ingress message from a NF is "1" MPS for OCNADD.

Benchmark Test Environment

The test environment specifications are listed below:
  • Ingress Traffic Rate: 135K MPS
  • The latency, resource utilization, and MPS is observed for the period of 3 hrs or more.
  • OCNADD single site deployment with ASM disabled
  • OCNADD Release 24.2.0 deployed over CNE (Bare metal) 23.3.4 version
  • Kafka Replication Factor (RF): 1
  • OCNADD Data Feed: TCP/TLS
  • OCNADD Kafka PVC: 400GB

    For more information about PVC requirements, see Kafka PVC Storage Requirements.

  • 3rd Party Application: With 2 End-points
  • cnDBTier Release 24.2.0
  • SEPP Release 24.2.0
  • SASL/SSL, enabled between NRF, SCP, SEPP and OCNADD
  • CNCC Release 24.2.0
  • Message Size: 3550 bytes
  • Environment: CNE (Bare metal)
  • Execution time: 12 Hours
  • cSEPP: PLMN Ingress Gateway messageCopy is enabled
  • pSEPP: The messageCopy feature is disabled

Benchmark Testcase Specifications

The testcase parameters are as follows:
  • OCNADD
    • A feed is configured using the OCNADD Console with aggregation rules set for SCP, NRF and SEPP.
    • Message Ingestion Rate: 135K MPS
    Resource Specifications:

    Table 4-13 OCNADD Resource Specifications

    Services CPU Request Per Pod CPU Limit Per Pod Memory Request Per Pod (Gi) Memory Limit Per Pod (Gi) min Replicas max Replicas Kafka Topic Partitions and Retention
    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 -
    ocnadduirouter 2 2 1 1 1 1 -
    ocnaddscpaggregation 2 2 4 4 6 6

    36 (SCP)/

    retention.ms = 300000
    ocnaddnrfaggregation 2 2 2 2 2 2

    12 (NRF)/

    retention.ms = 300000
    ocnaddseppaggregation 2 2 4 4 3 3

    18 (SEPP)/

    retention.ms = 300000
    ocnaddadapter 3 3 24 24 15 15

    135 (MAIN)/

    retention.ms = 300000
    ocnaddkafka 7.5 7.5 96 96 6 6 -
    zookeeper 1 1 2 2 3 3 -
    ocnaddgui 2 2 1 1 1 1 -
  • SEPP

    SEPP Traffic: 30K TPS using two trigger points.

  • SCP

    SCP Traffic: 90K TPS using two trigger points.

  • NRF

    NRF Traffic: 15K TPS using two trigger points.

Benchmark Test Results

Traffic Feed Details

Table 4-14 Traffic Feed Details

NF NF Traffic Copy Trigger Points Traffic Rate Duration in hours E2E Traffic Feed Average Latency E2E Traffic Feed Success Rate
OCNADD NA 135K MPS 12

Feed-1: 8.9 msec

Feed-2: 7.44 msec

Feed-1: 99.97%

Feed-2: 99.97%
NRF 2 Ingress Gateway (Request and Response)

2 - Egress Gateway (Request and Response)

 15K MPS 12 NA 99.99%
SCP 2 Ingress Gateway (Request and Response)

2 Egress Gateway (Request and Response)

 90K MPS 12 NA 99.96%
SEPP 2 PLMN Ingress Gateway (Request and Response) 30K MPS 12 NA 99.98%

CPU and Memory Utilization

The following table describes the OCNADD CPU and memory utilization:

Table 4-15 OCNADD CPU and Memory Utilization

Microservice/ Container Pod Count CPU Utilization (%) Memory Utilization (%)
ocnaddfilter 1 0.14% 13.20%
ocnaddnrfaggregation 2 60.50% 42.50%
ocnaddscpaggregation 6 79.90% 27.80%
ocnaddseppaggregation 3 68.60% 24.00%
feed-dd1-adapter 15 80.20% 22.40%
kafka-broker 6 91.40% 27.40%
zookeeper 3 0.12% 32.80%
feed-dd2-adapter 15 82.70% 16.60%
ocnaddadminservice 1 0.07% 35.20%
ocnaddalarm 1 0.06% 21.70%
ocnaddconfiguration 1 0.09% 41.70%
ocnaddexport 1 0.01% 2.27%
ocnaddgui 1 0.00% 2.48%
ocnaddhealthmonitoring 1 0.18% 36.70%
ocnadduirouter 1 0.01% 30.90%

4.6 Performance Benchmarking with 135K MPS SCP Traffic with Synthetic Feed Replication

The performance benchmarking test is performed on OCNADD with 135K MPS SCP traffic (67.5K TPS with 2 trigger points):

The benchmarking results are provided below:

Note:

One Ingress message from a NF is "1" MPS for OCNADD.

Benchmark Test Environment

The test environment specifications are listed below:
  • Ingress Traffic Rate: 135K MPS
  • The latency, resource utilization, and MPS is observed for the period of 3 hrs or more.
  • OCNADD single site deployment with ASM disabled
  • OCNADD Release 24.2.0 deployed over CNE (Bare metal) 23.3.4 version
  • Kafka Replication Factor (RF): 1
  • OCNADD Data Feed: TCP/TLS
  • OCNADD Kafka PVC: 400GB

    For more information about PVC requirements, see Kafka PVC Storage Requirements.

  • 3rd Party Application: With 2 End-points
  • cnDBTier Release 24.2.0
  • SCP Release 24.2.0
  • SASL/SSL, enabled between NRF, SCP, SEPP and OCNADD
  • CNCC Release 24.2.0
  • Message Size: 3550 bytes
  • Environment: CNE (Bare metal)
  • Execution time: 12 Hours

Benchmark Testcase Specifications

The testcase parameters are as follows:
  • OCNADD
    • A feed is configured using the OCNADD Console with aggregation rules set for SCP, NRF and SEPP.
    • Message Ingestion Rate: 135K MPS
    Resource Specifications:

    Table 4-16 OCNADD Resource Specifications

    Services CPU Request Per Pod CPU Limit Per Pod Memory Request Per Pod (Gi) Memory Limit Per Pod (Gi) min Replicas max Replicas Kafka Topic Partitions and Retention
    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 -
    ocnadduirouter 2 2 1 1 1 1 -
    ocnaddscpaggregation 2 2 4 4 8 8

    48 (SCP)/

    retention.ms = 300000
    ocnaddnrfaggregation 2 2 2 2 2 2

    6 (NRF)/

    retention.ms = 300000
    ocnaddseppaggregation 2 2 4 4 3 3

    6 (SEPP)/

    retention.ms = 300000
    ocnaddadapter 3 3 6 6 11 11

    66(MAIN)/

    retention.ms = 300000
    ocnaddkafka 7.5 7.5 96 96 6 6 -
    zookeeper 1 1 2 2 3 3 -
    ocnaddgui 2 2 1 1 1 1 -
  • SCP

    SCP Traffic: 67.5K TPS using two trigger points.

Benchmark Test Results

Traffic Feed Details

Table 4-17 Traffic Feed Details

NF NF Traffic Copy Trigger Points Traffic Rate Duration in hours E2E Traffic Feed Average Latency E2E Traffic Feed Success Rate
OCNADD NA 135K MPS 12

Feed-1: 26.9 msec

Feed-2: 26.5 msec

Feed-1: 99.98%

Feed-2: 99.98%
SCP 2 Ingress Gateway (Request)

2 Egress Gateway (Request)

 135K MPS 12 NA 99.98%

CPU and Memory Utilization

The following table describes the OCNADD CPU and memory utilization:

Table 4-18 OCNADD CPU and Memory Utilization

Micro-Service/ Container Pod Count CPU Utilization (%) Memory Utilization (%)
ocnaddfilter 1 50.00% 45.80%
ocnaddnrfaggregation 2 0.06% 16.20%
ocnaddscpaggregation 6 78.50% 28.40%
ocnaddseppaggregation 3 0.06% 10.70%
feed-dd1-adapter 11 76.40% 31.70%
kafka-broker 6 81.40% 37.90%
zookeeper 3 0.13% 19.90%
feed-dd2-adapter 11 75.50% 29.80%
ocnaddadminservice 1 0.12% 32.20%
ocnaddalarm 1 0.18% 20.50%
ocnaddconfiguration 1 0.11% 41.70%
ocnaddexport 1 0.02% 2.04%
ocnaddgui 1 0.00% 2.24%
ocnaddhealthmonitoring 1 0.19% 36.30%
ocnadduirouter 1 0.01% 30.40%