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 (OCNADD). The message feed feature is tested with SCP, NRF, SEPP, BSF, and PCF as the source of the message feed.

4.1 vCNE Cluster Environment

This section gives the details of the performance tests done in LBVM vCNE Cluster Environment.

4.1.1 Performance Benchmarking for 360K MPS SCP and 450K Egress Traffic with TCP and HTTP2 Feed

This performance benchmarking evaluates the deployment of OCNADD handling an SCP traffic of 360K MPS and Egress traffic of 450K MPS. The benchmark utilizes 3 TCP feeds and 1 HTTP2 feed:

The benchmarking results are provided below:

Note:

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

Benchmark Test Environment

Execution Details

  • Execution Time: 12+ Hours

Call Rate

  • Total Traffic: 360K MPS

Call Mix

  • Model: SCP Model-C

Setup Details

  • Environment: OCCNE 24.3.1
  • Cluster: vCNE
  • OCNADD Version: 25.1.200
  • cnDBTier: 24.3.0
  • NF Version: 25.1.100
  • Third-Party Application: One endpoint configured

Configuration Details

  • SCP: Worker messageCopy enabled
  • SASL/SSL: Enabled between SCP and OCNADD
  • OCNADD Replication Factor: 1
  • OCNADD Data Feed: HTTP2
  • OCNADD Kafka PVC: 400 Gi
  • Average Message Size: 3564 Bytes

Benchmark Testcase Specifications

The testcase parameters are as follows:
  • OCNADD
    • A feed is configured using the OCNADD Console with SCP.
    • Message Ingestion Rate: 360K MPS
    Resource Specifications:

    Table 4-1 Resource Specifications

    Services Min CPU Per Pod Max CPU Per Pod Min Memory Per Pod (Gi) Max Memory Per Pod (Gi) Min Replicas Max Replicas Paritions/Retention Topics
    ocnaddconfiguration 1 1 1 1 1 1 - -
    ocnaddalarm 1 1 1 1 1 1 - -
    ocnaddadminservice 1 1 1 1 1 1 - -
    ocnaddhealthmonitoring 1 1 1 1 1 1 - -
    ocnaddscpaggregation 2 2 4 4 13 13 78 SCP
    tcpfeed-adapter 3 3 6 6 20 20 120 MAIN
    tcpfeed-2-adapter 3 3 10 10 7 7 120 MAIN
    tcpfeed-3-adapter 3 3 10 10 7 7 120 MAIN
    http2feed-adapter 3 3 28 28 5 5 120 MAIN
    ocnaddkafka 5 5 96 96 16 16 - -
    kraft-controller 1 1 2 2 3 3 - -
    ocnaddgui 1 2 1 1 1 2 - -
    ocnadduirouter 1 2 1 1 1 2 - -
    ocnaddfilter 2 2 3 3 1 1 - -
    ocnaddexport 2 4 4 64 1 2 - -
  • SCP: SCP Traffic is 180K 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 360K MPS 12 http: 8ms

tcp(360k): 20ms

tcp(18k): 10ms

 Feed: 99.99%
SCP Worker 180K TPS 12 NA 99.99%

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 CPU Utilization (%) Memory Utilization (%) Total Replica
ocnaddscpaggregation 77 20 13
tcpfeed-adapter 75.40 38.97 20
tcpfeed-2-adapter 81 31 7
tcpfeed-3-adapter 85 21 7
http2feed-adapter 80.60 58.52 5
kafka-broker 31 10.6 16
kraft-controller 3 51 3
zookeeper 0 0 0
ocnaddadminservice 0.20 36.80 1
ocnaddalarm 0.20 45.10 1
ocnaddconfiguration 0.10 47.60 1
ocnaddexport 0.10 56.90 1
ocnaddgui 0.10 3.30 1
ocnaddhealthmonitoring 0.20 38.80 1
ocnadduirouter 0.10 34.80 1

4.1.2 Performance Benchmarking for 360K MPS SCP Traffic with Synthetic (TCP) Feed

This performance benchmarking evaluates the deployment of OCNADD handling an SCP traffic of 360K MPS. The benchmark utilizes a TCP feed:

The benchmarking results are provided below:

Note:

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

Benchmark Test Environment

Execution Details

  • Execution Time: 12+ Hours

Call Rate

  • Total Traffic: 360K MPS

Call Mix

  • Model: SCP Model-C

Setup Details

  • Environment: OCCNE 24.3.1
  • Cluster Topology:
    • DD: Cluster-1
    • NF: Cluster-2
    • Third-Party Consumers: Cluster-3
  • OCNADD Version: 25.1.200
  • cnDBTier: 25.1.100
  • SCP Version: 25.1.100
  • Third-Party Application: One endpoint configured

Configuration Details

  • SCP: Default configuration

Security & Data Feed

  • OCNADD Replication Factor: 1
  • OCNADD Data Feed: Synthetic (TCP)
  • OCNADD Kafka PVC: 400 GB
  • Average Message Size: ~3500 Bytes

Benchmark Testcase Specifications

The testcase parameters are as follows:
  • OCNADD
    • A feed is configured using the OCNADD Console with SCP.
    • Message Ingestion Rate: 360K MPS
    Resource Specifications:

    Table 4-4 OCNADD Resource Specifications

    Services Min CPU Per Pod Max CPU Per Pod Memory Request Per Pod (Gi) Max Memory Per Pod (Gi) Min Replicas Max Replicas Paritions/Retention Topics
    ocnaddconfiguration 1 1 1 1 1 1 - -
    ocnaddalarm 1 1 1 1 1 1 - -
    ocnaddadminservice 1 1 1 1 1 1 - -
    ocnaddhealthmonitoring 1 1 1 1 1 1 - -
    ocnaddscpaggregation 2 2 4 4 13 13 78 SCP
    ocnaddadapter 3 3 6 6 20 20 120 MAIN
    ocnaddkafka 5 5 48 48 11 11 - -
    kraft-controller 1 1 2 2 3 3 - -
    ocnaddgui 1 2 1 1 1 2 - -
    ocnadduirouter 1 2 1 1 1 2 - -
  • SCP: SCP Traffic is 180K 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 360K MPS 12 22.6ms Feed: 99.99%
SCP Ingress Gateway (Request)

Egress Gateway (Request)

 180K TPS 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

Micro-Service/ Container CPU Utilization (%) Memory Utilization (%) Total Replica
ocnaddscpaggregation 77 20 13
TCP: adapter (360k) 78.4 36.97 20
kafka-broker 35 15 11
kraft-controller 5 48 3
ocnaddadminservice 0.2 36.8 1
ocnaddalarm 0.2 45.1 1
ocnaddconfiguration 0.1 47.6 1
ocnaddgui 0.1 3.3 1
ocnaddhealthmonitoring 0.2 38.8 1
ocnadduirouter 0.1 34.8 1

4.2 Bare Metal Cluster Environment

This section gives the details of the performance tests done in Bare Metal Cluster Environment.

4.2.1 CNLB

This section gives the details of the performance tests done in CNLB Bare Metal Cluster Environment.

4.2.1.1 Performance Benchmarking for 360K MPS SCP and 450K Egress Traffic with Synthetic (TCP) and HTTP2 Feed

This performance benchmarking evaluates the deployment of OCNADD handling an SCP traffic of 360K MPS and Egress traffic of 450K MPS. The benchmark utilizes 3 synthetic (TCP) feeds and 1 HTTP2 feed:

The benchmarking results are provided below:

Note:

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

Benchmark Test Environment

  • Execution Time: 24+ Hours
  • Call Rate: 360K MPS
  • Call Mix: SCP Model-C

Setup Details

  • Environment: OCCNE 24.3.1
  • Cluster Topology:
    • DD: Deployed in Cluster-1
    • NF: Deployed in Cluster-2
    • Third-Party Consumers: Deployed in Cluster-3
  • Component Versions:
    • OCNADD: 25.1.200
    • cnDBTier: 25.1.100
    • SCP Version: 25.1.100
    • Third-Party Consumers: Two endpoints with two different egress NADs (configured in round-robin)

Configuration Details

  • SCP: messageCopy enabled
  • Security: SASL/SSL enabled between SCP and OCNADD
  • OCNADD:
    • Replication Factor: 1
    • Kafka PVC Size: 400 GB
  • Data Feed Configuration:
    • TCP Feed: Ingress 360K and Egress 360K
    • TCP Filtered Feed (1): Ingress 360K and Egress 36K
    • TCP Filtered Feed (2): Ingress 360K and Egress 36K
    • HTTP Filtered Feed: Ingress 360K and Egress 16K
  • Message Size: Approximately 3500–4000 bytes

Benchmark Testcase Specifications

The testcase parameters are as follows:
  • OCNADD
    • A feed is configured using the OCNADD Console with SCP.
    • Message Ingestion Rate: 360K MPS
    Resource Specifications:

    Table 4-7 Resource Specifications

    Services Min CPU Per Pod Max CPU Per Pod Min Memory Per Pod (Gi) Max Memory Per Pod (Gi) Min Replicas Max Replicas Paritions/Retention Topics
    ocnaddconfiguration 1 1 1 1 1 1 - -
    ocnaddalarm 1 1 1 1 1 1 - -
    ocnaddadminservice 1 1 1 1 1 1 - -
    ocnaddhealthmonitoring 1 1 1 1 1 1 - -
    ocnaddscpaggregation 2 2 4 4 13 13 78 SCP
    tcpfeedcnlb-sig1-sig2-egr1-adapter 3 3 6 6 20 20 120 MAIN
    tcpfeedcnlb-2-sig3-sig4-egr1-adapter 3 3 10 10 7 7 120 MAIN
    tcpfeedcnlb-sig3-sig4-egr1-adapter 3 3 10 10 7 7 120 MAIN
    http2feed-sig3-sig4-egr1-cnlb-adapter 3 3 28 28 5 5 120 MAIN
    ocnaddkafka 5 5 96 96 16 16 - -
    kraft-controller 1 1 2 2 3 3 - -
    ocnaddgui 1 2 1 1 1 2 - -
    ocnadduirouter 1 2 1 1 1 2 - -
    ocnadduirouter 1 2 1 1 1 2 - -
    ocnaddfilter 2 2 3 3 1 1 - -
  • SCP: SCP Traffic is 180K TPS using two trigger points.

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 360K MPS 24

httpfeed~ 21.6ms

tcp feed1~ 22.2ms

tcp feed3~ 28.5ms

tcp feed3~ 22.7ms

 NA
SCP Ingress Gateway (Request)

Egress Gateway (Request)

 180K TPS 24 NA NA

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 CPU Utilization (%) Memory Utilization (%) Total Replica
ocnaddscpaggregation 67.6 24.86 13
tcpfeedcnlb-sig1-sig2-egr1-adapter 65.55 36.25 20
tcpfeedcnlb-sig3-sig4-egr1-adapter 56.8 46.72 7
tcpfeedcnlb-2-sig3-sig4-egr1-adapter 56.85 46.72 7
http2feed-sig3-sig4-egr1-cnlb-adapter 65.6 55.52 5
kafka-broker 48.57 46.4 16
kraft-controller 0.5 47 3
ocnaddadminservice 0.1 36.8 1
ocnaddalarm 0.2 45.1 1
ocnaddconfiguration 0.2 47.6 1
ocnaddgui 0.1 3.3 1
ocnaddhealthmonitoring 0.2 38.8 1
ocnadduirouter 0.1 34.8 1
4.2.1.2 Performance Benchmarking for 360K MPS SCP Traffic with Synthetic (TCP) Feed

This performance benchmarking evaluates the deployment of OCNADD handling an SCP traffic of 360K MPS. The benchmark utilizes a synthetic (TCP) feed:

The benchmarking results are provided below:

Note:

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

Benchmark Test Environment

  • Execution Time: 48+ Hours
  • Call Rate: 360K MPS
  • Call Mix: SCP Model-C

Setup Details

  • Environment: OCCNE 24.3.1
  • Cluster Topology:
    • DD: Deployed in Cluster-1
    • NF: Deployed in Cluster-2
    • Third-Party Consumers: Deployed in Cluster-3
  • Component Versions:
    • OCNADD: 25.1.200
    • cnDBTier: 25.1.100
    • SCP Version: 25.1.100
    • Third-Party Consumers: Two endpoints with two different egress NADs (configured in round-robin)

Configuration Details

  • SCP: messageCopy enabled
  • Security: SASL/SSL enabled between SCP and OCNADD
  • OCNADD:
    • Replication Factor: 1
    • Data Feed Protocol: Synthetic (TCP)
    • Kafka PVC Size: 400 GB
  • Message Size: Approximately 3500–4000 bytes

Benchmark Testcase Specifications

The testcase parameters are as follows:
  • OCNADD
    • A feed is configured using the OCNADD Console with SCP.
    • Message Ingestion Rate: 360 K MPS
    Resource Specifications:

    Table 4-10 Resource Specifications

    Services Min CPU Per Pod Max CPU Per Pod Memory Request Per Pod (Gi) Min Memory Per Pod (Gi) Min Replicas Max Replicas Paritions/Retention Topics
    ocnaddconfiguration 1 1 1 1 1 1 - -
    ocnaddalarm 1 1 1 1 1 1 - -
    ocnaddadminservice 1 1 1 1 1 1 - -
    ocnaddhealthmonitoring 1 1 1 1 1 1 - -
    ocnaddscpaggregation 2 2 4 4 13 13 78 SCP
    ocnaddadapter 3 3 6 6 20 20 120 MAIN
    ocnaddkafka 5 5 48 48 16 16 - -
    kraft-controller 1 1 2 2 3 3 - -
    ocnaddgui 1 2 1 1 1 2 - -
    ocnadduirouter 1 2 1 1 1 2 - -
  • SCP: SCP Traffic is 180K TPS using two 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 360K MPS 48 19ms NA
SCP Ingress Gateway (Request)

Egress Gateway (Request)

 180K TPS 48 NA NA

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 CPU Utilization (%) Memory Utilization (%) Total Replica
ocnaddscpaggregation 57.50 18.75 13
adapter 55.66 26.25 20
kafka-broker 35.15 12.8 16
kraft-controller 0.20 46.70 3
ocnaddadminservice 0.20 36.80 1
ocnaddalarm 0.20 45.10 1
ocnaddconfiguration 0.10 47.60 1
ocnaddgui 0.10 3.30 1
ocnaddhealthmonitoring 0.20 38.80 1
ocnadduirouter 0.10 34.80 1
4.2.1.3 Performance Benchmarking for 270K MPS Aggregated Traffic with Synthetic (TCP) Feed

This performance benchmarking evaluates the deployment of OCNADD handling an aggregated feed of 270K MPS. The breakdown includes SCP traffic (64K TPS with 2 trigger points), NRF 15K MPS (7.5K TPS with 2 trigger points) and SEPP 60K MPS (15K TPS with 4 trigger points), BSF 10K MPS (with 2 trigger points) PCF 58K MPS (with 2 trigger points). The benchmark utilizes a synthetic (TCP) feed:

The benchmarking results are provided below:

Note:

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

Benchmark Test Environment

Execution Details

  • Execution Time: 12+ Hours

Call Rate

  • SCP Traffic: 128K MPS (64K TPS with 2 trigger points)
  • NRF: 15K MPS (7.5K TPS with 2 trigger points)
  • SEPP: 60K MPS (15K TPS with 4 trigger points)
  • BSF: 10K MPS (2 trigger points)
  • PCF: 58K MPS (2 trigger points)

Call Mix

  • NF Call Mix: SCP, NRF, SEPP, BSF and PCF NF Call mix models

Setup Details

  • Environment: OCCNE 24.3.1
  • Cluster Topology:
    • DD: Cluster-1
    • NF: Cluster-2
    • Third-Party Consumers: Cluster-3
  • OCNADD Version: 25.1.200
  • cnDBTier: 25.1.100

Network Functions (NFs)

  • SCP: 25.1.100
  • NRF: 25.1.100
  • SEPP: 25.1.100
  • BSF: 25.1.100
  • PCF: 25.1.100

Third-Party Consumers

  • Two endpoints with two different egress NADs (round-robin)

Configuration Details

  • NRF: Ingress Gateway and Egress Gateway messageCopy enabled
  • SCP: Default configuration
  • cSEPP:Ingress PLMN/N32 and Egress PLMN/N32 messageCopy enabled
  • pSEPP:messageCopy disabled
  • PCF: Ingress Gateway and Egress Gateway messageCopy enabled
  • BSF: Ingress Gateway and Egress Gateway messageCopy enabled

Security and Data Feed

  • SASL/SSL: Enabled between BSF and OCNADD
  • OCNADD Replication Factor: 1
  • OCNADD Data Feed: HTTP2
  • OCNADD Kafka PVC: 400 GB
  • Average Message Size: ~3500 Bytes

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, SEPP, BSF, and PCF.
    • Message Ingestion Rate: 270K MPS
    Resource Specifications:

    Table 4-13 OCNADD Resource Specifications

    Services Min CPU Per Pod Max CPU Per Pod Min Memory Per Pod (Gi) Max Memory Per Pod (Gi) Min Replicas Max Replicas Paritions/Retention Topics
    ocnaddconfiguration 1 1 1 1 1 1 - -
    ocnaddalarm 1 1 1 1 1 1 - -
    ocnaddadminservice 1 1 1 1 1 1 - -
    ocnaddhealthmonitoring 1 1 1 1 1 1 - -
    ocnaddscpaggregation 2 2 4 4 5 5 30 SCP
    ocnaddnrfaggregation 2 2 2 2 1 1 6 NRF
    ocnaddseppaggregation 2 2 4 4 3 3 18 SEPP
    ocnaddadapter 3 3 6 6 15 15 90 MAIN
    ocnaddkafka 4 4 48 48 11 11 - -
    kraft-controller 1 1 1 2 3 3 - -
    ocnaddgui 1 2 1 1 1 2 - -
    ocnadduirouter 1 2 1 1 1 2 - -
    ocnaddfilter 2 2 3 3 1 1 - -
    ocnaddexport 2 4 4 64 1 2 - -
    ocnaddpcfaggregation 2 2 2 2 3 3 18 PCF
    ocnaddbsfaggregation 2 2 2 2 1 1 6 BSF
  • SCP Traffic: 128K MPS (64K TPS with 2 trigger points)
  • NRF: 15K MPS (7.5K TPS with 2 trigger points)
  • SEPP: 60K MPS (15K TPS with 4 trigger points)
  • BSF: 10K MPS (2 trigger points)
  • PCF: 58K MPS (2 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 270K MPS 12 33.6ms Feed: 99.98%
PCF Ingress Gateway (Request)

Egress Gateway (Request)

 58K TPS 12 NA 99.99%
SCP Ingress Gateway (Request)

Egress Gateway (Request)

 128K TPS 12 NA 99.95%
BSF Ingress Gateway (Request)

Egress Gateway (Request)

 10K TPS 12 NA 100%
NRF Ingress Gateway (Request)

Egress Gateway (Request)

 15K TPS 12 NA 99.98%
SEPP Ingress plmn/n32 Gateway (Request)

Egress plmn/n32 Gateway (Request)

 60K TPS 12 NA 99.91%

CPU and Memory Utilization

The following table describes the OCNADD CPU and memory utilization:

Table 4-15 OCNADD CPU and Memory Utilization

Micro-Service/ Container CPU Utilization (%) Memory Utilization (%) Total Replica
ocnaddnrfaggregation 58.4 31.9 1
ocnaddpcfaggregation 55.2 27.8 3
ocnaddbsfaggregation 35.4 20.9 1
ocnaddscpaggregation 62.4 19.9 5
ocnaddseppaggregation 58.2 17.1 3
adapter 59.5 13.1 15
kafka-broker 57.2 11.6 11
kraft-controller 0.455 42.4 3
ocnaddadminservice 0.417 29.3 1
ocnaddalarm 0.137 33.7 1
ocnaddconfiguration 0.129 34.2 1
ocnaddgui 0.00100 3.32 1
ocnaddhealthmonitoring 0.382 33.8 1
ocnadduirouter 0.00838 29.5 1
4.2.1.4 Performance Benchmarking for 270K MPS Aggregated Traffic with HTTP2 Feed

This performance benchmarking evaluates the deployment of OCNADD handling an aggregated feed of 270K MPS. The breakdown includes 128K MPS SCP traffic (64K TPS with 2 trigger points), NRF 15K MPS (7.5K TPS with 2 trigger points) & SEPP 60K MPS (15K TPS with 4 trigger points), BSF 10K MPS (with 2 trigger points) PCF 58K MPS (with 2 trigger points). The benchmark utilizes an HTTP2 feed:

The benchmarking results are provided below:

Note:

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

Benchmark Test Environment

Execution Details

  • Execution Time: 12+ Hours

Call Rate

  • SCP Traffic: 128K MPS (64K TPS with 2 trigger points)
  • NRF: 15K MPS (7.5K TPS with 2 trigger points)
  • SEPP: 60K MPS (15K TPS with 4 trigger points)
  • BSF: 10K MPS (2 trigger points)
  • PCF: 58K MPS (2 trigger points)

Call Mix

  • NF Call Mix: SCP, NRF, SEPP, BSF and PCF NF Call mix models

Setup Details

  • Environment: OCCNE 24.3.1
  • Cluster Topology:
    • DD: Cluster-1
    • NF: Cluster-2
    • Third-Party Consumers: Cluster-3
  • OCNADD Version: 25.1.200
  • cnDBTier: 25.1.100

Network Functions (NFs)

  • SCP: 25.1.100
  • NRF: 25.1.100
  • SEPP: 25.1.100
  • BSF: 25.1.100
  • PCF: 25.1.100

Third-Party Consumers

  • Two endpoints with two different egress NADs
  • Load Balancing: Weighted (50–50% or 60–40% distribution)

Configuration Details

  • NRF: Ingress Gateway & Egress Gateway messageCopy enabled
  • SCP: Default configuration
  • cSEPP: Ingress PLMN/N32 and Egress PLMN/N32 messageCopy enabled
  • pSEPP: messageCopy disabled
  • PCF: Ingress Gateway & Egress Gateway messageCopy enabled
  • BSF: Ingress Gateway & Egress Gateway messageCopy enabled

Security & Data Feed

  • SASL/SSL: Enabled between BSF and OCNADD
  • OCNADD Replication Factor: 1
  • OCNADD Data Feed: HTTP2
  • OCNADD Kafka PVC: 400 GB
  • Average Message Size: ~3500 Bytes

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, SEPP, BSF, and PCF.
    • Message Ingestion Rate: 270K MPS
    Resource Specifications:

    Table 4-16 OCNADD Resource Specifications

    Services Min CPU Per Pod Max CPU Per Pod Memory Request Per Pod (Gi) Memory Limit Per Pod (Gi) Min Replicas Max Replicas Paritions/Retention Topics
    ocnaddconfiguration 1 1 1 1 1 1 - -
    ocnaddalarm 1 1 1 1 1 1 - -
    ocnaddadminservice 1 1 1 1 1 1 - -
    ocnaddhealthmonitoring 1 1 1 1 1 1 - -
    ocnaddscpaggregation 2 2 4 4 5 5 30 SCP
    ocnaddnrfaggregation 2 2 2 2 1 1 6 NRF
    ocnaddseppaggregation 2 2 4 4 3 3 18 SEPP
    ocnaddadapter 3 3 6 6 23 23 207 MAIN
    ocnaddkafka 4 4 48 48 11 11 - -
    kraft-controller 1 1 2 2 3 3 - -
    ocnaddgui 1 2 1 1 1 2 - -
    ocnadduirouter 1 2 1 1 1 2 - -
    ocnaddfilter 2 2 3 3 1 1 - -
    ocnaddexport 2 4 4 64 1 2 - -
    ocnaddpcfaggregation 2 2 2 2 2 2 12 PCF
    ocnaddbsfaggregation 2 2 2 2 1 1 6 BSF
  • SCP Traffic: 128K MPS (64K TPS with 2 trigger points)
  • NRF: 15K MPS (7.5K TPS with 2 trigger points)
  • SEPP: 60K MPS (15K TPS with 4 trigger points)
  • BSF: 10K MPS (2 trigger points)
  • PCF: 58K MPS (2 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 270K MPS 12 33.6ms Feed: 99.98%
PCF Ingress Gateway (Request)

Egress Gateway (Request)

 58K TPS 12 NA 99.99%
SCP Ingress Gateway (Request)

Egress Gateway (Request)

 128K TPS 12 NA 99.95%
BSF Ingress Gateway (Request)

Egress Gateway (Request)

 10K TPS 12 NA 100%
NRF Ingress Gateway (Request)

Egress Gateway (Request)

 15K TPS 12 NA 99.98%
SEPP Ingress plmn/n32 Gateway (Request)

Egress plmn/n32 Gateway (Request)

 60K TPS 12 NA 99.91%

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 CPU Utilization (%) Memory Utilization (%) Total Replica
ocnaddnrfaggregation 62.3 35.5 1
ocnaddpcfaggregation 61.8 30.7 2
ocnaddbsfaggregation 40.3 17.9 1
ocnaddscpaggregation 65.3 21.3 5
ocnaddseppaggregation 60.2 18.7 3
adapter 42.6 55.9 23
kafka-broker 61.1 42.6 11
kraft-controller 0.448 50.3 3
ocnaddadminservice 0.0581 28.5 1
ocnaddalarm 5.77 32.3 1
ocnaddconfiguration 0.135 34.1 1
ocnaddgui 0.000994 3.32 1
ocnaddhealthmonitoring 0.496 33.6 1
ocnadduirouter 0.00817 29.7 1

4.2.2 LBVM

This section gives the details of the performance tests done in LBVM Bare Metal Cluster Environment.

4.2.2.1 Performance Benchmarking for 135K MPS Traffic with Synthetic Feed Replication

This performance benchmarking evaluates a centralized deployment with a single worker group, handling an aggregated feed of 135K MPS. The breakdown includes 90K MPS for SCP (45K TPS with 2 trigger points), 30K MPS for SEPP (15K TPS with 2 trigger points), and 15K MPS for NRF (7.5K TPS with 2 trigger points). The benchmark utilizes a replicated synthetic feed:

The benchmarking results are provided below:

Note:

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

Benchmark Test Environment

  • Ingress Traffic Rate: 135K MPS
  • Observation Period: 3+ hours
  • Deployment: OCNADD single-site, ASM disabled
  • Kafka Replication Factor: 1
  • Kafka PVC: 400GB
  • Data Feed: Two TCP (Synthetic) Feeds (TLS enabled)
  • Third-Party Applications: 1 endpoint per feed
  • Software Versions:
    • cnDBTier: 24.3.0
    • SCP: 24.3.0
    • NRF: 24.3.0
    • SEPP: 24.3.0
    • CNCC: 24.3.0
  • Security: SASL/SSL enabled between NRF, SCP, SEPP, and OCNADD
  • Message Size: ~3500 Bytes
  • Execution Time: 24 hours
  • Call Mix: SCP, NRF, and SEPP NF CALL MIX models
Setup Details
  • Environment: OCCNE (Bare metal) 23.3.4
  • OCNADD: 25.1.100
Configuration
  • NRF: Ingress Gateway and Egress Gateway messageCopy enabled
  • SCP: Default configuration
  • cSEPP: PLMN Ingress Gateway messageCopy enabled
  • pSEPP: messageCopy disabled
  • OCNADD:

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-19 OCNADD Resource Specifications

    Services Min CPU Per Pod Max CPU Per Pod Min Memory Per Pod (Gi) Max Memory Per Pod (Gi) Min Replicas Max Replicas Paritions/Retention Topics
    ocnaddadapter 3 3 6 6 11 11 66 MAIN
    ocnaddadminservice 1 1 1 1 1 1 - -
    ocnaddalarm 1 1 1 1 1 1 - -
    ocnaddconfiguration 1 1 1 1 1 1 - -
    ocnaddexport 2 4 4 64 1 2 - -
    ocnaddgui 1 2 1 1 1 2 - -
    ocnaddhealthmonitoring 1 1 1 1 1 1 - -
    ocnaddkafka 7.5 7.5 96 96 6 6 - -
    ocnaddnrfaggregation 2 2 2 2 1 1 6 NRF
    ocnaddscpaggregation 2 2 4 4 5 5 30 SCP
    ocnaddseppaggregation 2 2 4 4 2 2 12 SEPP
    ocnadduirouter 1 2 1 1 1 2 - -
    zookeeper 1 1 1 2 3 3 - -
  • SCP: 90K MPS traffic (45K TPS with 2 trigger points)
  • NRF: 15K MPS traffic (7.5K TPS with 2 trigger points)
  • SEPP 30K MPS traffic (15K TPS with 2 trigger points)

Benchmark Test Results

Traffic Feed Details

Table 4-20 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 24

Feed-1: 26.9 msec

Feed-2: 26.5 msec

Feed-1: 99.98%

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

Egress Gateway (Request)

 45K TPS 24 NA 99.98%
NRF Ingress Gateway (Request)

Egress Gateway (Request)

 7.5K TPS 24 NA 99.98%
SEPP Ingress Gateway (Request)

Egress Gateway (Request)

 15K TPS 24 NA 99.98%

CPU and Memory Utilization

The following table describes the OCNADD CPU and memory utilization:

Table 4-21 OCNADD CPU and Memory Utilization

Micro-Service/ Container CPU Utilization (%) Memory Utilization (%) Total Replica
adapter-1 60.6 19.0 11
adapter-2 63.0 19.4 11
kafka-broker 40.1 25.8 6
ocnaddadminservice 0.138 24.1 1
ocnaddalarm 0.217 27.5 1
ocnaddconfiguration 0.164 34.9 1
ocnaddexport 0.0115 2.33 1
ocnaddgui 0.00108 3.12 1
ocnaddhealthmonitoring 0.530 34.5 1
ocnaddnrfaggregation 70.4 32.4 1
ocnaddscpaggregation 58.0 18.6 5
ocnaddseppaggregation 70.0 20.3 2
ocnadduirouter 0.00758 28.7 1
zookeeper 0.125 31.0 3
4.2.2.2 Performance Benchmarking for 270K MPS SCP Traffic with Synthetic Feed

This performance benchmarking evaluates a centralized deployment with a single worker group, handling an SCP Model-C traffic of 270K MPS. The benchmark utilizes a synthetic feed:

The benchmarking results are provided below:

Note:

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

Benchmark Test Environment

  • Ingress Traffic Rate: 270K MPS
  • Observation Period: 3+ hours
  • Deployment: OCNADD single-site, ASM disabled
  • Kafka Replication Factor: 1
  • Kafka PVC: 300GB
  • Data Feed: TCP (Synthetic)
  • Third-Party Applications: 1 endpoint per feed
  • Software Versions:
    • cnDBTier: 24.3.0
    • NRF: 24.3.0
    • CNCC: 24.3.0
  • Security: SASL/SSL enabled between between SCP and OCNADD
  • Message Size: ~3500 - 4000 Bytes
  • Execution Time: 14 hours
  • Call Mix: SCP Model-C
Setup Details
  • Environment: OCCNE (Bare metal) 23.3.4
  • OCNADD: 25.1.100
Configuration
  • SCP: Default configuration, messageCopy enabled
  • OCNADD:

Benchmark Testcase Specifications

The testcase parameters are as follows:
  • OCNADD
    • A feed is configured using the OCNADD Console with SCP.
    • Message Ingestion Rate: 270K MPS
    Resource Specifications:

    Table 4-22 OCNADD Resource Specifications

    Services Min CPU Per Pod Max CPU Per Pod Min Memory Per Pod (Gi) Max Memory Per Pod (Gi) Min Replicas Max Replicas Paritions/Retention Topics
    ocnaddadapter(TCPs) 3 3 6 6 21 21 126 MAIN
    ocnaddadminservice 1 1 1 1 1 1 - -
    ocnaddalarm 1 1 1 1 1 1 - -
    ocnaddconfiguration 1 1 1 1 1 1 - -
    ocnaddexport 2 4 4 64 1 2 - -
    ocnaddgui 1 2 1 1 1 2 - -
    ocnaddhealthmonitoring 1 1 1 1 1 1 - -
    ocnaddkafka 5 5 48 48 11 11 - -
    ocnaddscpaggregation 2 2 4 4 11 11 66 SCP
    ocnadduirouter 1 2 1 1 1 2 - -
    zookeeper 1 1 1 2 3 3 - -
  • SCP: SCP Traffic is 135K TPS using two trigger points.

Benchmark Test Results

Traffic Feed Details

Table 4-23 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 14

51.1 msec

99.99%
SCP Ingress Gateway (Request)

Egress Gateway (Request)

 135K MPS 14 NA 99.98%

CPU and Memory Utilization

The following table describes the OCNADD CPU and memory utilization:

Table 4-24 OCNADD CPU and Memory Utilization

Micro-Service/ Container CPU Utilization (%) Memory Utilization (%) Total Replica
ocnaddscpaggregation 65.5 29.8 11
ocnaddadapter(TCPs) 58.1 29.0 21
kafka-broker 44.1 60.5 11
zookeeper 0.152 33.7 3
ocnaddadminservice 0.134 27.9 1
ocnaddalarm 0.399 18.4 1
ocnaddconfiguration 0.232 33.9 1
ocnaddexport 0.0183 2.21 1
ocnaddgui 0.00110 3.12 1
ocnaddhealthmonitoring 0.710 33.2 1
ocnadduirouter 0.00812 25.3 1
4.2.2.3 Performance Benchmarking for 270K MPS SCP Traffic with Kafka Feed

This performance benchmarking evaluates a centralized deployment with a single worker group, handling an SCP traffic of 270K MPS. The benchmark utilizes a Kafka feed:

The benchmarking results are provided below:

Note:

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

Benchmark Test Environment

  • Ingress Traffic Rate: 270K MPS
  • Observation Period: 3+ hours
  • Deployment: OCNADD single-site, ASM disabled
  • Kafka Replication Factor: 1
  • Kafka PVC: 300GB
  • Data Feed: Kafka-feed
  • Third-Party Consumers: 1 endpoint per feed
  • Software Versions:
    • cnDBTier: 24.3.0
    • SCP: 24.3.0
    • CNCC: 24.3.0
  • Security: SASL/SSL enabled between between SCP and OCNADD
  • Message Size: ~3500 - 4000 Bytes
  • Execution Time: 12 hours
  • Call Mix: SCP SCP Model-C
Setup Details
  • Environment: OCCNE (Bare metal) 23.3.4
  • OCNADD: 25.1.100
Configuration
  • SCP: Default configuration, messageCopy enabled
  • OCNADD:

Benchmark Testcase Specifications

The testcase parameters are as follows:
  • OCNADD
    • A feed is configured using the OCNADD Console with SCP.
    • Message Ingestion Rate: 270 K MPS
    Resource Specifications:

    Table 4-25 Resource Specifications

    Services Min CPU Per Pod Max CPU Per Pod Memory Request Per Pod (Gi) Max Memory Per Pod (Gi) Min Replicas Max Replicas Paritions/Retention Topics
    ocnaddadapter - - - - - - 261 MAIN
    ocnaddadminservice 1 1 1 1 1 1 - -
    ocnaddalarm 1 1 1 1 1 1 - -
    ocnaddconfiguration 1 1 1 1 1 1 - -
    ocnaddexport 2 4 4 64 1 2 - -
    ocnaddgui 1 2 1 1 1 2 - -
    ocnaddhealthmonitoring 1 1 1 1 1 1 - -
    ocnaddkafka 5 5 48 48 11 11 - -
    ocnaddscpaggregation 2 2 4 4 11 11 66 SCP
    ocnadduirouter 1 2 1 1 1 2 - -
    zookeeper 1 1 1 2 3 3 - -
  • SCP: SCP Traffic is 135K TPS using two trigger points.

Benchmark Test Results

Traffic Feed Details

Table 4-26 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 12

Feed-1: 26.9 msec

Feed-2: 26.5 msec

Feed-1: 99.98%

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

Egress Gateway (Request)

 135K TPS 12 NA 99.98%

CPU and Memory Utilization

The following table describes the OCNADD CPU and memory utilization:

Table 4-27 OCNADD CPU and Memory Utilization

Micro-Service/ Container CPU Utilization (%) Memory Utilization (%) Total Replica
kafka-broker 46.1 16.3 11
ocnaddadminservice 0.0855 25.9 1
ocnaddalarm 0.80 26.8 1
ocnaddconfiguration 0.139 33.2 1
ocnaddexport 0.0115 2.18 1
ocnaddgui 0.000999 3.10 1
ocnaddhealthmonitoring 0.339 35.0 1
ocnaddscpaggregation 68.2 27.9 11
ocnadduirouter 0.00654 54.0 1
zookeeper 0.121 28.8 3
4.2.2.4 Performance Benchmarking for 9K BSF Traffic with HTTP2 Feed
The performance benchmarking test is performed on OCNADD with 9K traffic with HTTPS feed. The traffic includes:
  • BSF Traffic: 9K MPS
  • Enabled BSF Ingress Gateway and Egress Gateway Message Copy Feature.

The benchmarking results are provided below:

Note:

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

Benchmark Test Environment

  • Ingress Traffic Rate: 9K MPS
  • Observation Period: 3+ hours
  • Deployment: OCNADD single-site, ASM disabled
  • Kafka Replication Factor: 1
  • Kafka PVC: 30GB
  • Data Feed: HTTP2
  • Third-Party Applications: 1 endpoint per feed
  • Software Versions:
    • cnDBTier: 24.3.0
    • BSF: 24.3.0
    • CNCC: 24.3.0
  • Security: SASL/SSL enabled between between BSF and OCNADD
  • Message Size: ~1200 Bytes
  • Execution Time: 12 hours
  • Call Mix: Binding-Create/Delete
Setup Details
  • Environment: OCCNE (Bare metal) 23.3.4
  • OCNADD: 25.1.100
Configuration
  • BSF: Ingress Gateway and Egress Gateway messageCopy enabled
  • OCNADD:

Benchmark Testcase Specifications

The testcase parameters are as follows:
  • OCNADD
    • A feed is configured using the OCNADD Console with BSF.
    • Message Ingestion Rate: 9K MPS
    Resource Specifications:

    Table 4-28 OCNADD Resource Specifications

    Services Min CPU Per Pod Max CPU Per Pod Min Memory Per Pod (Gi) Max Memory Per Pod (Gi) Min Replicas Max Replicas Paritions/Retention Topics
    ocnaddadapter 3 3 4 4 1 1 9 MAIN
    ocnaddadminservice 1 1 1 1 1 1 - -
    ocnaddalarm 1 1 1 1 1 1 - -
    ocnaddbsfaggregation 3 3 4 4 1 1 6 BSF
    ocnaddconfiguration 1 1 1 1 1 1 - -
    ocnaddexport 2 4 4 64 1 2 - -
    ocnaddfilter 2 2 3 3 1 1 - -
    ocnaddgui 1 2 1 1 1 2 - -
    ocnaddhealthmonitoring 1 1 1 1 1 1 - -
    ocnaddkafka 2 2 24 24 4 4 - -
    ocnadduirouter 1 2 1 1 1 2 - -
    zookeeper 1 1 1 2 3 3 - -
  • BSF : BSF Traffic: 4.5K TPS using two trigger points.

Benchmark Test Results

Traffic Feed Details

Table 4-29 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 12

20.20ms

Feed: 100%
BSF Ingress Gateway (Request)

Egress Gateway (Request)

 4.5K TPS 12 NA 100%

CPU and Memory Utilization

The following table describes the OCNADD CPU and memory utilization:

Table 4-30 OCNADD CPU and Memory Utilization

Micro-Service/ Container CPU Utilization (%) Memory Utilization (%) Total Replica
adapter 33.5 32.1 1
kafka-broker 12.3 11.4 4
ocnaddadminservice 0.287 27.5 1
ocnaddalarm 0.0963 37.7 1
ocnaddbsfaggregation 31.0 22.1 1
ocnaddconfiguration 0.110 36.7 1
ocnaddexport 0.00686 2.32 1
ocnaddgui 0.00107 3.13 1
ocnaddhealthmonitoring 0.0898 35.1 1
ocnadduirouter 0.00664 29.5 1
zookeeper 0.122 27.0 3
4.2.2.5 Performance Benchmarking for 30K MPS PCF Traffic with HTTP2 Feed
The performance benchmarking test is performed on OCNADD with 31K MPS traffic with HTTP2 feed. The traffic includes:
  • PCF Traffic: 30K MPS
  • Enabled PCF Ingress Gateway and Egress Gateway Message Copy Feature.

The benchmarking results are provided below:

Note:

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

Benchmark Test Environment

  • Ingress Traffic Rate: 30K MPS
  • Observation Period: 3+ hours
  • Deployment: OCNADD single-site, ASM disabled
  • Kafka Replication Factor: 1
  • Kafka PVC: 50GB
  • Data Feed: HTTP2
  • Third-Party Applications: 1 endpoint per feed
  • Software Versions:
    • cnDBTier: 24.3.0
    • PCF: 24.3.0
    • CNCC: 24.3.0
  • Security: SASL/SSL enabled between between PCF and OCNADD
  • Message Size: ~2079 Bytes
  • Execution Time: 12 hours
  • Call Mix: Session Management (SM) traffic
Setup Details
  • Environment: OCCNE (Bare metal) 23.3.4
  • OCNADD: 25.1.100
Configuration
  • PCF: Ingress Gateway and Egress Gateway messageCopy enabled
  • OCNADD:

Benchmark Testcase Specifications

The testcase parameters are as follows:
  • OCNADD
    • A feed is configured using the OCNADD Console with PCF.
    • Message Ingestion Rate: 30K MPS
    Resource Specifications:

    Table 4-31 OCNADD Resource Specifications

    Services Min CPU Per Pod Max CPU Per Pod Min Memory Per Pod (Gi) Max Memory Per Pod (Gi) Min Replicas Max Replicas Paritions/Retention Topics
    ocnaddadapter 3 3 4 4 3 3 27 MAIN
    ocnaddadminservice 1 1 1 1 1 1 - -
    ocnaddalarm 1 1 1 1 1 1 - -
    ocnaddpcfaggregation 2 2 2 2 2 2 12 PCF
    ocnaddconfiguration 1 1 1 1 1 1 - -
    ocnaddexport 2 4 4 64 1 2 - -
    ocnaddfilter 2 2 3 3 1 1 - -
    ocnaddgui 1 2 1 1 1 2 - -
    ocnaddhealthmonitoring 1 1 1 1 1 1 - -
    ocnaddkafka 2 2 24 24 4 4 - -
    ocnadduirouter 1 2 1 1 1 2 - -
    zookeeper 1 1 1 2 3 3 - -
  • PCF : PCF Traffic: 15K TPS using two trigger point.

Benchmark Test Results

Traffic Feed Details

Table 4-32 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

33.6ms

Feed: 99.99%
PCF Ingress Gateway (Request)

Egress Gateway (Request)

 15K TPS 12 NA 99.99%

CPU and Memory Utilization

The following table describes the OCNADD CPU and memory utilization:

Table 4-33 OCNADD CPU and Memory Utilization

Micro-Service/ Container CPU Utilization (%) Memory Utilization (%) Total Replica
httpsfeed-adapter 51.6 62.10 3
kafka-broker 50.8 18.10 4
ocnaddadminservice 0.08 33.90 1
ocnaddalarm 0.12 19.30 1
ocnaddconfiguration 0.09 40.70 1
ocnaddexport 0.03 2.05 1
ocnaddgui 0.00 3.09 1
ocnaddhealthmonitoring 0.13 35.70 1
ocnaddpcfaggregation 61.4 32.90 2
ocnadduirouter 0.01 32.50 1
zookeeper 0.14 48.20 3