4 Benchmark Testing

This section describes the environment used for benchmarking Oracle Communications Cloud Native Core, Network Repository Function (NRF). Benchmarking is performed with the settings described in this section.

The default values or recommendations for any required software or resource are available from third-party vendors. The operators may choose different values.

4.1 Overview

To qualify the test run, the following elements are considered:

  • Pod restart
  • CPU and Memory utilization
  • Error rate
  • Ingress and egress traffic rate
  • Success rate
  • Message request and response processing time
  • Infrastructure resource requirements and utilization

4.2 NRF Features

The following table lists the features that are enabled during benchmarking.

Table 4-1 NRF Features

NRF Features Feature Status Notes
Subscriber Location Function ENABLED

SLF is enabled for 3 NfTypes (AUSF, UDR, and UDM) in slfLookupConfig.
SLF Selection from Registered NF Profiles ENABLED

Dynamic SLF feature is enabled.
Access Token Caching during SLF Query ENABLED

Access Token Caching during SLF Query is enabled with 24 hour validity period based caching. For more information about the accessTokenCacheEnabled under slfOptions, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

Overload Control ENABLED

This feature must be configured with the recommended values as mentioned in the Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

Note: No feature specific failures are induced in the performance test.

Preferred Locality Feature Set ENABLED

Extended Preferred locality is configured with 2 locationTypes, 8 locationMappings, 56 preferredLocationDetails.
NRF Forwarding per NF Type/Service Type ENABLED for UDM

Forwarding is enabled for discovery services. 1 host is present in nrfHostConfig and 1 rule is present in forwardingRulesConfig.
EmptyList in Discovery Response ENABLED

EmptyList feature is enabled and discoveryValidityPeriodCfg under nfDiscoveryOptions is configured with 5 rules.

Note: No feature specific failures are induced in the performance test.

Access Token Request Authorization ENABLED

AuthFeature is enabled with 8 rules in authRulesConfig under nfAccessTokenOptions.
Pod Protection Support for NRF Subscription Microservice ENABLED

This feature must be configured with the recommended values as mentioned in the Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

Note: No feature specific failures are induced in the performance test.

Subscription Limit ENABLED

Set the subscription limit to 1000. For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

User-Agent Header for Outgoing Requests ENABLED

For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

NRF to Pick Port from ipEndpoints and FQDN from the NF Service or NF level when Selecting SLF ENABLED

For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

ASM Sidecar ENABLED

For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

Maximum Number of Profiles in Discovery Response ENABLED

Set the value as 12 for the profilesCountInDiscoveryResponse parameter. For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

Note: If the value is greater than 12, there will be a performance impact.

NRF Georedundancy ENABLED

For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

NRF Growth ENABLED

For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

SLF Routing using SCP ENABLED

For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

Discovery Validity ENABLED

Discovery validity feature is enabled with a value as 1 minute (for all NF Types).

For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

Access Token Expiry Time NA

The expiry duration for a NRF signed certificate. The limit is 24 hours.

For more information about NRF Access Token Service Usage Details, see Oracle Communications Cloud Native Core, Network Repository Function User Guide.

Load Change Threshold for Notifications from NRF NA

This feature is configured using nfNotifyLoadThreshold parameter. Set the value to 10%.

For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

Monitoring the Availability of SCP Using SCP Health APIs ENABLED

For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

Note: No feature specific failures are induced in the performance test.

NRF to Retry Alternate Producer to Support Maximum Diversity NA

The value of maxSlfAttempts parameter is set to 1 and the value of useAlternateScp parameter is set to true.

For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

Note: No feature specific failures are induced in the performance test.

Support for TLS DISABLED

For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade, and Fault Recovery Guide.
Error Response Enhancement NA

For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

Error Log Enhancements ENABLED

For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

NRF support for A_PFD DataSetId in registration and discovery (DataSetId Enhancements) ENABLED

For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

NFService Priority Update ENABLED

For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

Subscriber Identity in messages (3GPP-SBI-Correlation-Info) ENABLED

For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

Ingress Gateway Pod Protection DISABLED

For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

Egress Gateway Pod Throttling DISABLED

For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade and Fault Recovery Guide.

NF Profile Size Limit ENABLED

For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

Ingress Gateway Pod Protection Using Rate Limiting ENABLED

This feature must be configured with the recommended values as mentioned in the Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

Note:
  • The Ingress Gateway Pod Protection using Rate Limiting feature is recommended over the Egress Gateway Pod Throttling feature.
  • No feature specific failures are induced in the performance test.
Egress Gateway Pod Protection Using Rate Limiting ENABLED

This feature must be configured with the recommended values as mentioned in the Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

Note:
  • The Egress Gateway Pod Protection using Rate Limiting feature is recommended over the Egress Gateway Pod Throttling feature.
  • No feature specific failures are induced in the performance test.
Rerouting SLF Requests Based on Server Header Value ENABLED

For more information about the configuration, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

Note: No feature specific failures are induced in the performance test.

Note:

  • Apart from these features being enabled, rest of the feature configurations have been set to their default values. For more information about the feature configurations, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide. For more information about the features, see Oracle Communications Cloud Native Core, Network Repository Function User Guide.
  • No feature specific failures are induced in the performance test.

4.3 Software Test Constraints

Table 4-2 Software Test Constraints

Test Constraint Details
NRF Version 25.2.201
Average HTTP Request Packet Size ~630 to 15000 bytes (Based on NfRegister Request)
Average HTTP Response Packet Size ~5500-131000 bytes (Discovery Response with nfProfiles)
Average NF Heartbeats Timer per NF 30s
Average size of NF Profiles ~630 to 15000 bytes

4.4 Service Operations

This section list the various service operations with the required query parameters.

NfDiscover Service Operation

The NfDiscover service operations are sent with the following query parameters:

  • Target-nf-type, guami, and requester-nssais
  • Target-nf-type, requester-nf-type, routing-indicator, and group-id-list
  • Target-nf-type, requester-nf-type, supi, and service-names
  • Target-nf-type, requester-nf-type, and service-names
  • Target-nf-type, requester-nf-type, and group-id-list
  • Target-nf-type and pgw
  • Target-nf-type, requester-nf-type, supi, and service-names
  • Target-nf-type, requester-nf-type, and service-names
  • Target-nf-type, dnn, snssai, TAI, and pgw-ind
  • Target-nf-type, SUPI, group-id-list, and service-names
  • Target-nf-type, dnn, snssai, preferred-locality, and service-names
  • Target-nf-type and guami
  • Target-nf-type, requester-nf-type, and preferred-locality
  • Target-nf-type, requester-nf-type, preferred-locality, and SUPI
  • Target-nf-type, requester-nf-type, SUPI, group-id-list, requester-nf-type, and data-set
  • Target-nf-type, requester-nf-type, routing-indicator, group-id-list, and service-names
  • Target-nf-type, servicenames, requester-nf-type, requester-nf-instance-fqdn, requester-plmn-list, and guami
  • Target-nf-type, requester-nf-typ, and target-nf-instance-id
  • Target-nf-type, requester-nf-type, target-nf-instance-id, and service_name
  • Target-nf-type, requester-nf-type, target-nf-instance-id, and notification-type
  • Target-nf-type, requester-nf-type, dnn, snssais, preferred-locality, ue-ipv4-address, ip-domain, and ue-ipv6-prefix
  • Target-nf-type, requester-nf-type, service-names, requester-nf-instance-fqdn, requester-plmn-list, preferred-locality, notification-type, n1-msg-class, and client-type
  • Target-nf-type, requester-nf-type, gpsi, and preferred-locality
  • Target-nf-type, requester-nf-type, service-names, requester-nf-instance-fqdn, requester-plmn-list, preferred-locality, and gpsi
  • Target-nf-type, requester-nf-type, service-names, gpsi, and preferred-locality

4.5 53K TPS per NRF Set/106K TPS for Two NRF Sets

The per set capacity of NRF is 53K TPS. Higher TPS rate can be achieved by deploying additional NRF sets. This section provides the details for 106K TPS.

4.5.1 NRF Services Resource Requirements

This section provides the NRF services resource requirement per NRF deployment.

Note:

Changes in the resource requirements are highlighted in bold.

Table 4-3 NRF Services Resource Requirements

Service Name Min Pod Replica Max Pod Replica Min CPU/Pod Max CPU/Pod Min Memory/Pod (in Gi) Max Memory/Pod (in Gi) Min (Mi) Ephemeral Storage Max (Gi) Ephemeral Storage
Helm test 1 1 1 2 1 2 78.1 1
<helm-release-name>-nfregistration 2 2 4 4 3 3 78.1 1
<helm-release-name>-nfdiscovery 2 42 8 8 5 5 78.1 2
<helm-release-name>-nfsubscription 2 2 2 2 3 3 78.1 1
<helm-release-name>-nrfauditor 2 2 2 2 3 3 78.1 1
<helm-release-name>-nrfconfiguration 1 1 2 2 2 2 78.1 1
<helm-release-name>-nfaccesstoken 2 2 2 2 2 2 78.1 1
<helm-release-name>-nrfartisan 1 1 2 2 2 2 78.1 1
<helm-release-name>-nrfcachedata 2 2 4 4 4 4 78.1 1
<helm-release-name>-ingressgateway 2 30 4 4 5 5 78.1 1
<helm-release-name>-egressgateway 2 30 4 4 4 4 78.1 1
<helm-release-name>-alternate-route 2 2 2 2 4 4 78.1 1
<helm-release-name>-appinfo 2 2 1 1 1 1 78.1 1
<helm-release-name>-perfinfo 2 2 1 1 1 1 78.1 1

Table 4-4 Service Mesh Sidecar Resource Requirements

Service Name CPU/Pod Memory/Pod (in G) Concurrency
Min Max Min Max
Helm test 0 0 0 0 NA
<helm-release-name>-nfregistration 2 2 3 3 2
<helm-release-name>-nfdiscovery 2 2 3 3 4
<helm-release-name>-nfsubscription 2 2 3 3 2
<helm-release-name>-nrfauditor 2 2 3 3 2
<helm-release-name>-nrfconfiguration 2 2 3 3 2
<helm-release-name>-nfaccesstoken 2 2 3 3 2
<helm-release-name>-nrfartisan 2 2 3 3 2
<helm-release-name>-nrfcachedata 2 2 3 3 2
<helm-release-name>-ingressgateway 4 4 3 3 8
<helm-release-name>-egressgateway 4 4 3 3 8
<helm-release-name>-alternate-route 2 2 3 3 2
<helm-release-name>-appinfo 2 2 3 3 2
<helm-release-name>-perfinfo 2 2 3 3 2

4.5.2 cnDBTier Resource Requirements per NRF Deployment

This section provides the details of cnDBTier services resource requirements.

Note:

Changes in the resource requirements are highlighted in bold.
The following table describes the resources required by cnDBTier pods to perform NRF benchmark tests.

Table 4-5 cnDBTier Services Resource Requirements

Service Name Pod Replica # CPU/Pod Memory/Pod (in Gi) PVC Size (in Gi) Ephemeral Storage
Min Min Max Min Max PVC1 PVC2 Min (Mi) Max (Gi)
db-monitor-svc 1 4 4 4 4 0 NA 200 1
db-replication-svc (leader) 1 2 2 12 12 4 NA 200 1
db-replication-svc (other) 1 1.1 1.1 2 2 0 NA 200 1
db-backup-manager-svc 1 1.1 1.1 1 1 0 NA 200 1
ndbappmysqld (Access) 2 8 8 3 3 1 NA 200 1
ndbmgmd (Mgmt) 2 4 4 10 10 15 NA 200 1
ndbmtd (Data) 4 4 4 5 5 4 5 200 1
ndbmysqld (SQL Replication) 4 4 4 20 20 90 NA 200 1

The following table describes the resources required by cnDBTier service mesh sidecar to perform NRF benchmark tests.

Table 4-6 Service Mesh Sidecar

Service Name CPU Memory (in Gi) Concurrency
Min Max Min Max
db-monitor-svc 2 2 1 1 2
db-replication-svc (leader) 2 2 1 1 2
db-replication-svc (other) 2 2 1 1 2
db-backup-manager-svc 2 2 1 1 2
ndbappmysqld (Access) 4 4 1 1 8
ndbmgmd (Mgmt) 2 2 1 1 8
ndbmtd (Data) 2 2 1 1 8
ndbmysqld (SQL Replication) 2 2 1 1 8

The following default values are added for the service mesh specific annotations in the ocnrf_dbtier_CNDBTIER_VERSION_custom_values_NRF_VERSION.yaml file.

The following table describes the default values for resources required by cnDBTier service mesh sidecar to perform NRF benchmark tests.

Table 4-7 Default Values for Service Mesh Specific Annotations

Parameter Name Annotations
mgm.annotations 

sidecar.istio.io/inject: "true"
sidecar.istio.io/proxyCPU: "2"
sidecar.istio.io/proxyCPULimit: "2"
sidecar.istio.io/proxyMemory: "1Gi"
sidecar.istio.io/proxyMemoryLimit: "1Gi"
proxy.istio.io/config: '{concurrency: 8}'
traffic.sidecar.istio.io/excludeInboundPorts: "8081"
ndb.annotations 

sidecar.istio.io/inject: "true"
sidecar.istio.io/proxyCPU: "2"
sidecar.istio.io/proxyCPULimit: "2"
sidecar.istio.io/proxyMemory: "1Gi"
sidecar.istio.io/proxyMemoryLimit: "1Gi"
proxy.istio.io/config: '{concurrency: 8}'
traffic.sidecar.istio.io/excludeInboundPorts: "8081"
api.annotations 

sidecar.istio.io/inject: "true"
sidecar.istio.io/proxyCPU: "2"
sidecar.istio.io/proxyCPULimit: "2"
sidecar.istio.io/proxyMemory: "1Gi"
sidecar.istio.io/proxyMemoryLimit: "1Gi"
proxy.istio.io/config: '{concurrency: 8}'
traffic.sidecar.istio.io/excludeInboundPorts: "8081"
ndbapp.annotations 

sidecar.istio.io/inject: "true"
sidecar.istio.io/proxyCPU: "4"
sidecar.istio.io/proxyCPULimit: "4"
sidecar.istio.io/proxyMemory: "1Gi"
sidecar.istio.io/proxyMemoryLimit: "1Gi"
proxy.istio.io/config: '{concurrency: 8}'
traffic.sidecar.istio.io/excludeInboundPorts: "8081"
db-replication-svc.podAnnotations 

sidecar.istio.io/inject: "true"
sidecar.istio.io/proxyCPU: "2"
sidecar.istio.io/proxyCPULimit: "2"
sidecar.istio.io/proxyMemory: "1Gi"
sidecar.istio.io/proxyMemoryLimit: "1Gi"
proxy.istio.io/config: '{concurrency: 2}'

Note: The annotations for db-replication-svc.podAnnotations varies depending on the replication cardinality. podAnnotations should be added for each such replication deployment section in the ocnrf_dbtier_CNDBTIER_VERSION_custom_values_NRF_VERSION.yaml file.

db-replication-svc.podAnnotations traffic.sidecar.istio.io/excludeInboundPorts: "8081"

The inbound ports are added only to the db-replication-svc (leader pod).
db-monitor-svc.podAnnotations 

sidecar.istio.io/inject: "true"
sidecar.istio.io/proxyCPU: "2"
sidecar.istio.io/proxyCPULimit: "2"
sidecar.istio.io/proxyMemory: "1Gi"
sidecar.istio.io/proxyMemoryLimit: "1Gi"
proxy.istio.io/config: '{concurrency: 2}'
traffic.sidecar.istio.io/excludeInboundPorts: "8081"
db-backup-manager-svc.pod.annotations 

sidecar.istio.io/inject: "true"
sidecar.istio.io/proxyCPU: "2"
sidecar.istio.io/proxyCPULimit: "2"
sidecar.istio.io/proxyMemory: "1Gi"
sidecar.istio.io/proxyMemoryLimit: "1Gi"
proxy.istio.io/config: '{concurrency: 2}'

4.5.3 State Data Quantum at NRF

4.5.3.1 NF Count Per NF Types

The total number of NFs supported by per NRF set is 300. For two sets a total of 600 NFs are supported.

The following table lists the NF count per NF type along with the NF profile size.

Table 4-8 NF Count Per NF Types

Target-NF Types NF Count Profile Size (in bytes)
AMF 46 15000
AUSF 48 4640
BSF 3 1700
CBCF 3 11300
CHF 3 1800
GMLC 3 0630
LMF 3 2400
NEF 3 11300
PCF 79 1500-2500
SCP 27 1200
SEPP 3 300
SLF 3 2100
SMF 148 15000
SMSF 3 11300
UDM 48 3200
UDR 177 1700-2000
4.5.3.2 NF Subscription Count

The total number of NF subscriptions supported by per NRF set is 750. For two sets a total of 1500 NFs are supported. The following table lists the NF subscription count.

Table 4-9 NF Subscription Count

Subscription Type Subscription Count
Subscription to a set of NF Instances identified by their NF Type 412
Subscription to a set of NF Instances identified by their NF Instance Id 211
Subscription to a set of NF Instances identified by their NF Set Id 127

Note:

  • Subscriptions are configured with NotificationCondition to monitor only the “/priority” or “/load” attributes.
  • The reqNotifEvents include NF_REGISTERED, NF_DEREGISTERED, and NF_PROFILE_CHANGE, ensuring notifications for status change events and relevant profile updates.

4.5.4 Call-Mix

This section describes the various type of service requests with the required traffic distribution and targeted TPS per NRF set.

Table 4-10 Call-Mix

S.No Type of Request Traffic Type Traffic Distribution (in %) Targeted TPS
A NF Register Ingress 0.0094 5
B NF Update Ingress 0.090 43
C NF Heartbeat Ingress - 155
D NF Subscribe + Update Subscription Ingress 0.037 20
E NF Discover Ingress 97.17 51600
F NRF Forwarded Discovery (Incoming) Ingress 10% of Incoming discovery traffic 0
G % of traffic forwarded to remote PLMN (case Visited NRF) Ingress 0 Not included in this test.
H % of traffic received from remote PLMN (case Home NRF) Ingress 0 Not included in this test.
I SLF Query Egress 88.4% of Discovery 45600
J NF Access Token for SLF Egress Extra 1
K NF Profile Retrieval Ingress 2.29 1210
L NF List Retrieval Ingress 0.036 19
M NF Status Notify Egress 4.55 2155
N NF Status UnSubscribe Ingress 0.0057 3
O NF DeRegister Ingress 0.0057 3
P NF Access Token for Consumers Ingress 0.0188 10
Q NRF Forwarding (Outgoing) Egress 15% of Discovery 7740

Table 4-11 Total Traffic

Traffic Type Message Considered Targeted TPS
Total Incoming Traffic A + B + C + D + E + F + G + H + J + K + L + N + O + P 53068
Total Outgoing Traffic I +J+ M + Q 55495
4.5.4.1 Discovery TPS per NfType and Number of Profiles in Response

The following table indicates the discovery TPS per NfType per NRF set and the number of profiles sent in the response.

Table 4-12 Discovery TPS per NfType and Number of Profiles in Response

Target-Nf Types TPS (in %) Absolute Discovery TPS SLF Queries Posted Number of Profiles in Response
AMF 4.24 2281 0 4
AUSF 0.39 209 0 6
BSF 0.00 0 0 3
CBCF 0.00 0 0 3
CHF 0.077 42.3 0 3
GMLC 0.00 0 0 4
LMF 0.025 14.5 0 4
NEF 0.026 14.1 0 3
PCF 0.39 211 0 10
SLF 0 0 0 3
SMF 8.09 4368 0 4
SMSF 0.025 13.5 0 3
UDM 85.5 46209 46209 6
UDR 1.21 652 652 12

4.5.5 Test Observations

This section following table provides the details of test duration used for the benchmarking test.

Table 4-13 Test Observations

Parameter Values
Test Duration 48 hours
TPS Achieved 53608
Ingress Gateway incoming connections from the NF Peers (from the Ingress Gateway ASM sidecar to Ingress Gateway application container) 256
Ingress Gateway outgoing connections towards the backend services (from the Ingress Gateway application container to Ingress Gateway ASM sidecar) 2.4K
Egress Gateway incoming connections from the backend services (from the Egress Gateway ASM sidecar to Egress Gateway application container) 240
Egress Gateway outgoing connections towards NF Peers (from the Egress Gateway application container to Egress Gateway sidecar) 1.2K

4.5.6 NRF Resource Utilization

The following table describes NRF microservices and their utilization for 53K TPS per NRF set with 600 NFs in two sets.

Table 4-14 NRF Resource Utilization

NRF Microservices Number of Pods Min CPU Max CPU Average CPU Min Memory Max Memory Average Memory
nfdiscovery 42 52.2% 53.6% 52.9% 51.5% 51.9% 51.7%
ingressgateway 30 56.3% 57.9% 57.4% 65.7% 67.4% 66.7%
egressgateway 30 51.5% 53.0% 52.3% 43.0% 44.1% 43.7%
nfregistration 2 26% 30.4% 30% 37.0% 37.8% 37.4%
nfsubscription 2 14.6% 17.5% 16.8% 32.7% 33.2% 33%
nrfauditor 2 0.434% 0.582% 0.54% 17.8% 18.1% 17.9%
nfaccesstoken 2 1.88% 2.05% 1.92% 37.4% 37.9% 37.6%
nrfcachedata 2 35.2% 36.6% 35.9% 49.8% 53.8% 53%
alternate-route 2 0.0758% 0.103% 0.08% 16.9% 16.9% 16.9%
perf-info 2 6.63% 7.71% 7.67% 14.1% 14.2% 14.1%
appinfo 2 4.42% 4.74% 4.48% 28.5% 28.5% 28.5%
nrfconfiguration 1 1.61% 1.89% 1.65% 37.4% 37.9% 37.7%
nrfartisan 1 0.106% 0.150% 0.10% 22.7% 22.8% 22.7%

Note:

If you enable Message Feed feature at Ingress Gateway and Egress Gateway, approximately 33% pod capacity is impacted. The features enabled for this benchmark testing does not utilize alternate-route service.

4.5.7 cnDBTier Services Resource Utilization

The following table provides observed values of cnDBTier services.

Table 4-15 cnDBTier Services Resource Utilization

Service Name Pod Count Min CPU Max CPU Average CPU Min Memory Max Memory Average Memory
ndbappmysqld (Access) 2 6.45% 16.4% 11.5% 28.5% 28.7% 28.6%
ndbmtd (Data) 4 6.21% 9.87% 8.98% 91.1% 91.2% 91.2%
ndbmgmd (Mgmt) 2 0.116% 0.193% 0.172% 2.19% 2.20% 2.19%
db-monitor-svc 1 0.192% 1.03% 0.304% 21.4% 22.0% 21.6%
db-backup-manager-svc 1 0.152% 1.30% 0.217% 21.3% 22.2% 21.4%

Table 4-16 cnDBTier Statistics

DBTier Statistics Value
Disk Write operations per second 1208
Disk Read operations per second 4897
Transaction rates on data nodes 2416

4.5.8 Latency Observations

This section provides information about the latency observations.

Table 4-17 Consolidated Latency Metrics Across Discovery Service

Latency Parameter Details
99th Percentile (ms) 95th Percentile (ms) 90th Percentile (ms) 50th Percentile (ms)
Average Turnaround time at Ingress Gateway, Discovery Processing, and SLF Egress Transaction 206 195 191 151
Average Turnaround time for Discovery Processing and SLF Egress Transaction 200 195 190 150
Average Turnaround time for SLF Egress Transaction (see Note) 199 195 190 150

Note:

Following simulators are used for performance measurement and their induced latency:
  • NF simulator to NRF: 50 ms
  • NRF to forwarding simulator and forwarding simulator to NRF: 150 ms
  • NRF to SLF: 150 ms

The latency value of Min, Max, and Average for discovery service operation is maximum among all the other service operations.

Table 4-18 Consolidated Latency Metrics Across Non-discovery Service Operations

Service Operation Latency Parameter 99th Percentile (ms) 95th Percentile (ms) 90th Percentile (ms) 50th Percentile (ms)
NfStatusSubscribe (POST) Average Turnaround time at Ingress for all subscription service operations 41.9 1.90 1.80 1.00
NfStatusSubscribe (PATCH) Average Turnaround time at Ingress for all subscription service operations 79.5 53.9 42.8 26.2
NfStatusUnsubscribe Average Turnaround time at Ingress for all subscription service operations 64.0 39.3 29.7 16.3
NfAccessToken Latency observed at Ingress gateway for all access token service operations 29.7 19.3 17.8 8.91
NfRegistration (PUT) Latency observed at Ingress for NfRegister/NfUpdate 63.7 39.6 38.0 27.4
NfUpdate (PATCH) Latency observed at Ingress for NfRegister/NfUpdate 49.5 29.6 28.7 21.4
NfDeregister Latency observed at Ingress for NfDeregister 50.1 20.2 19.4 15.2
NFProfileRetrieval Latency observed at Ingress for NfProfileRetrieval 29.2 17.2 12.0 6.69
NfListRetrieval Latency observed at Ingress for NfListRetrieval 29.2 17.2 12.0 6.69