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%