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 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-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 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-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 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-3 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%

4.2 Performance Benchmarking with 270K MPS SCP Traffic with Synthetic Feed

The performance benchmarking test is performed on OCNADD with 270K MPS SCP traffic (135K 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: 270K 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.3.0 deployed over CNE (Bare metal) 23.3.4 version
  • Kafka Replication Factor (RF): 1
  • OCNADD Data Feed: TCP/syntheticfeed
  • 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.3.0
  • SCP Release 24.3.0
  • SASL/SSL, enabled between SCP and OCNADD
  • CNCC Release 24.3.0
  • Message Size: 3400 bytes
  • Environment: CNE (Bare metal)
  • Execution time: 48 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.
    • Message Ingestion Rate: 270K 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.5 2.5 4 4 11 11

    66 (SCP)/

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

    126(MAIN)/

    retention.ms = 300000
    ocnaddkafka 5 5 48 48 11 11 -
    zookeeper 1 1 2 2 3 3 -
    ocnaddgui 1 1 1 1 1 1 -
  • SCP

    SCP Traffic: 135K 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 270K MPS 48

51.1 msec

99.99%
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-6 OCNADD CPU and Memory Utilization

Micro-Service/ Container Pod Count CPU Utilization (%) Memory Utilization (%)
ocnaddbsfaggregation 1 0.05% 19.00%
ocnaddfilter 1 0.09% 12.40%
ocnaddnrfaggregation 1 0.06% 15.50%
ocnaddscpaggregation 11 82.60% 29.40%
feed-dd1-adapter 21 85.40% 28.40%
kafka-broker 11 74.00% 19.50%
zookeeper 3 0.16% 24.20%
ocnaddadminservice 3 0.07% 33.50%
ocnaddalarm 1 1.11% 25.00%
ocnaddconfiguration 1 0.09% 43.20%
ocnaddexport 1 0.02% 2.15%
ocnaddgui 1 0.00% 3.05%
ocnaddhealthmonitoring 1 0.21% 37.90%
ocnadduirouter 1 0.01% 32.80%

4.3 Performance Benchmarking for 9K MPS BSF Traffic with Message Copy

The performance benchmarking test is performed on OCNADD with 9K traffic with HTTPS feed. The traffic includes:
  • BSF Traffic: 4.5K MPS
  • Enabled Gateway Features: Oauth, Overload Control, and SBI Correlation Info Header

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: 9K 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.3.0 deployed over vCNE 24.3.0 version
  • Kafka Replication Factor (RF): 1
  • OCNADD Data Feed: https
  • OCNADD Kafka PVC: 25GB

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

  • 3rd Party Application: With 1 End-point
  • cnDBTier Release 24.2.1
  • BSF Release 24.3.0
  • SASL/SSL, enabled between BSF and OCNADD
  • Message Size: 1600 bytes
  • Environment: vCNE
  • Execution time: 48 Hours

Benchmark Testcase Specifications

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

    Table 4-7 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 2 1 1 -
    ocnaddadmin 1 1 1 1 1 1 -
    ocnaddhealthmonitoring 1 1 1 1 1 1 -
    ocnadduirouter 2 2 1 1 1 1 -
    ocnaddbsfaggregation 2 2 2 2 1 1 6 (BSF)/

    retention.ms=300000
    ocnaddscpaggregation 2 2 4 4 1 1 -
    ocnaddnrfaggregation 2 2 2 2 1 1 -
    ocnaddseppaggregation 2 2 2 2 1 1 -
    ocnaddadapter 3 3 4 4 2 2 18 (MAIN)/

    retention.ms=300000
    ocnaddkafka 2 2 24 24 4 4 -
    zookeeper 1 1 2 2 3 3 -
    ocnaddgui 2 2 1 1 1 1 -
  • BSF

    BSF Traffic: 4.5K TPS using one trigger point.

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 NA 9K MPS 48

115ms

Feed: 99.99%
SCP 2 Ingress Gateway (Request)

2 Egress Gateway (Request)

 4.5K MPS 48 NA 99.99%

CPU and Memory Utilization

The following table describes the OCNADD CPU and memory utilization:

Table 4-9 OCNADD CPU and Memory Utilization

Micro-Service/ Container Pod Count CPU Utilization (%) Memory Utilization (%)
ocnaddfilter 1 0.128% 22.5%
ocnaddnrfaggregation 1 0.584% 18.9%
ocnaddbsfaggregation 1 23.8% 24.9%
ocnaddscpaggregation 1 0.386% 15.5%
ocnaddseppaggregation 1 0.685% 15.9%
https-feed-adapter 2 19.5% 8.43%
kafka-broker 4 25.8% 14.9%
zookeeper 3 0.115% 30.80%
ocnaddadminservice 1 0.0497% 38.7%
ocnaddalarm 1 0.0606% 21.3%
ocnaddconfiguration 1 0.0625% 42.0%
ocnaddexport 1 0.0132% 2.12%
ocnaddgui 1 0.00134% 3.11%
ocnaddhealthmonitoring 1 0.0774% 37.70%
ocnadduirouter 1 0.00667% 34.0%