4.3 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 23.4.0 deployed over CNE (Bare metal) 22.3.0 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 23.4.0
  • SEPP Release 23.4.0
  • SASL/SSL, enabled between SEPP and OCNADD
  • CNCC Release 23.4.0
  • Message Size: 3300 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-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 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 1 1

    24 (SEPP)/

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

    126 (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 -
  • SEPP

    SEPP Traffic: 60K TPS using four 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 60K MPS 12

Feed-1: 2.39 msec

Feed-2: 2.27 sec

Feed-1: 99.99%

Feed-2: 99.99%
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-9 OCNADD CPU and Memory Utilization

Microservice/ Container Pod Count CPU Utilization (%) Memory Utilization (%)
ocnaddadminservice 1 0.15% 29.00%
ocnaddalarm 1 1.42% 22.00%
ocnaddconfiguration 1 0.16% 35.20%
ocnaddgui 1 0.00% 3.02%
ocnaddhealthmonitoring 1 0.35% 37.70%
ocnadduirouter 1 0.23% 30.50%
feed-dd1-adapter 14 42.50% 17.00%
kafka-broker 4 84.10% 39.70%
zookeeper 4 0.16% 16.70%
feed-dd2-adapter 14 41.00% 17.60%
ocnaddfilter 4 49.40% 15.20%
ocnaddnrfaggregation 1 0.06% 14.10%
ocnaddscpaggregation 1 0.06% 14.80%
ocnaddseppaggregation 4 75.20% 59.50%