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 Bare Metal Cluster Environment

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

4.1.1 Performance Benchmarking for 1.5M MPS SCP traffic with Single Synthetic Feed with two endpoints

This performance benchmarking evaluates the deployment of OCNADD handling a SCP traffic of 1.5M MPS. The benchmark utilizes single synthetic (TCP) feed, with tow endpoints.

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: 1.5M MPS
  • Call Mix: SCP Model-C + Model-D 20%
Setup Details
  • Environment: OCCNE 25.1.200
  • LB Type: Bare metal CNLB
  • Cluster Topology:
    • DD: Deployed in Cluster-1
    • NF: Within the same cluster as DD
    • Third-Party Consumers: Within the same cluster as DD
  • Component Versions:
    • OCNADD: 25.2.200
    • cnDBTier: 25.2.101
    • SCP Version: 25.2.100
    • Third-Party Consumers: Two endpoints (configured in round-robin)
Configuration Details
  • SCP: messageCopy enabled
  • Security: SASL/SSL enabled between SCP and OCNADD
  • OCNADD:
    • Replication Factor: 1
    • Kafka RAM Storage(Relay): 160 GB
    • Kafka RAM Storage(Mediation): 100 GB
  • Data Feed Configuration:
    • TCP Feed (1): Ingress 1.5M and Egress 1.5M
  • Message Size: Approximately 3000–4000 bytes
Benchmark Testcase Specifications

The testcase parameters are as follows:

  • OCNADD
    • A feed is configured using the OCNADD Console with SCP NF.
    • Message Ingestion Rate: 1.5M 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 - -
ocnaddhealthmonitoring 1 1 1 1 1 1 - -
ocnaddgui 1 1 1 1 1 1 - -
ocnadduirouter 1 1 1 1 1 2 - -
ocnaddmanagementgateway 1 1 1 1 1 2 - -
Relay Agent Services
kraft-controller 1 1 2 2 3 3 - -
ocnaddkafka (kafkaBroker) 6 6 160 160 20 20 - -
ocnaddscpaggregation 3 3 8 8 57 57 342 SCP
ocnaddrelayagentgateway 1 1 1 1 1 2 - -
Mediation Services
kraft-controller 1 1 2 2 3 3 - -
ocnaddkafka (kafkaBroker) 7 7 100 100 20 20 - -
ocnaddadapter-1(TCP) (consumeradapter) 6 6 6 6 59 59 354 MAIN
ocnaddadminservice 1 1 1 1 1 1 - -
ocnaddmediationgateway 1 1 1 1 1 2 - -
  • SCP: SCP Traffic is 750K 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 1.5M MPS 24h+ ocnaddadapter-1(TCP) 46.4 ms 99.97%
SCP Ingress Gateway (Request)

Egress Gateway (Request)

 500K TPS 24h+ NA NA

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
ocnaddconfiguration 0.16% 40.63% 1
ocnaddalarm 0.08% 45.31% 1
ocnaddhealthmonitoring 0.28% 32.03% 1
ocnaddgui 0.00% 3.48% 1
ocnadduirouter 0.07% 17.87% 1
ocnaddmanagementgateway 0.15% 21.78% 1
Relay Agent Services
kraft-controller 0.8% 59.8% 3
ocnaddkafka (kafkaBroker) 48.9% 57.4% 20
ocnaddscpaggregation 52.7% 15.1% 57
ocnaddrelayagentgateway 0.2% 26.4% 1
Mediation Services
kraft-controller 0.77% 57.17% 3
ocnaddkafka (kafkaBroker) 53.44% 52.66% 20
ocnaddadapter-1(TCP) (consumeradapter) 66.83% 21.47% 59
ocnaddadminservice 0.12% 25.98% 1
ocnaddmediationgateway 0.10% 22.17% 1