4.1 Performance Benchmarking with HTTP2 Feed

The performance benchmarking test is performed on OCNADD with 64K MPS HTTP2 egress feed which includes 40K MPS SCP traffic (20K TPS with 2 traffic copy trigger points on SCP), 9K MPS NRF traffic (4.5K TPS with 2 traffic copy trigger points on NRF) and 15K MPS SEPP traffic (7.5K 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: 64K 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.2.0 deployed over CNE (Bare metal) 22.3.0 version
  • Kafka Replication Factor (RF): 1
  • OCNADD Data Feed: HTTP2/TLS
  • OCNADD Kafka PVC: 300GB

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

  • 3rd Party Application: 1 Perfgo Server with 2 End-points
  • cnDBTier Release 23.2.0
  • NRF Release 23.1.0
  • SCP Release 23.2.0
  • SEPP Release 23.1.0
  • SASL/SSL, enabled between NRF/SCP/SEPP and OCNADD
  • CNCC Release 23.2.0
  • Message Size: 3490 Bytes
  • Environment: CNE (Bare metal)

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: 64K 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
    ocnaddadapter 3 3 4 4 8 8

    72 (MAIN)/

    retention.ms=300000
    ocnaddadmin 1 1 1 1 1 1  
    ocnaddalarm 1 1 1 1 1 1  
    ocnaddcache 1 1 10 10 2 2  
    ocnaddconfiguration 1 1 1 1 1 1  
    ocnaddgui 2 2 1 1 1 1  
    ocnaddhealthmonitoring 1 1 1 1 1 1  
    ocnaddkafka 5 5 48 48 3 3  
    ocnaddnrfaggregation (9K) 2 2 2 2 1 1

    6 (NRF)/

    retention.ms=300000
    ocnaddscpaggregation (40K) 2 2 2 2 2 2

    12 (SCP)/

    retention.ms=300000
    ocnaddseppaggregation (15K) 2 2 2 2 1 1

    6 (SEPP)/

    retention.ms=300000
    ocnaduirouter 2 2 1 1 1 1  
    zookeeper 1 1 2 2 3 3  
  • SCP

    SCP Traffic: 20K TPS using two trigger points.

  • NRF

    NRF Traffic: 4.5K TPS using two trigger points.

  • SEPP

    SEPP Traffic: 7.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 64K MPS 12 2.66 ms 99.94%
NRF 2 (IGW/EGW) 9K MPS 12   99.90%
SCP 2 (Request Ingress/Request Egress) 40K MPS 12   99.98%
SEPP 2 (PLMN IGW) 15K MPS 12   99.98%

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 (%)
ocnaddadapter 8 71.2 25.3
ocnaddkafka 3 87.6 18.1
ocnaddadmin 1 0.195 26.5
ocnaddalarm 1 0.546 18.3
ocnadduirouter 1 0.0410 24.6
ocnaddconfiguration 1 0.130 28.8
ocnaddhealthmonitoring 1 0.222 27.1
ocnaddgui 1 0.033 4.70
ocnaddnrfaggregation (9K) 1 73.8 44.3
ocnaddscpaggregation (40K) 2 79.9 59.2
ocnaddseppaggregation (15K) 1 80.7 35.4
zookeeper 3 0.270 14.2
ocnaddcache 2 0.202 6.89