3 UDR Benchmark Testing

This chapter describes UDR, SLF, and EIR test scenarios.

3.1 Test Scenario 1: SLF Call Model: 34k lookup TPS + 1.44k Provisioning TPS

This test scenario describes performance and capacity of SLF functionality offered by UDR and provides the benchmarking results for various deployment sizes. This test scenario reflects the resource requirements for a single site in a four-site georedanduncy model.

The following features are enabled for SLF in this testcase:
  • Overload Handling
  • Support for LCI and OCI Header
  • Network Function Scoring for a Site
  • Conflict Resolution
  • Ingress Gateway Pod Protection Using Rate Limiting
  • Support for Default Group ID in SLF
  • Support for User-Agent Header
The following feature is enabled for Provisioning Gateway in this testcase:
  • Auditor Service
You can perform benchmark tests on SLF for compute and storage resources by considering the following conditions:
  • Signaling (SLF Look Up): 34K TPS
  • Provisioning: 1.44 K
  • Total Subscribers: 20 Million
  • Profile Size: 700 bytes
The following table describes the benchmarking parameters and their values:

Table 3-1 Traffic Model Details

Request Type Details TPS
Lookup 34k SLF Lookup GET Requests 34K
Provisioning (1.44K using Provgw) CREATE 210
DELETE 210
UPDATE 510
GET 510
The following table describes the testcase parameters and their values:

Table 3-2 Testcase Parameters

Input Parameter Details Configuration Values
SLF Version Tag 25.2.201
Target TPS 34K Lookup + 1.44K Provisioning
Traffic Profile SLF 34K Profile
SLF Response Timeout 900ms
The following table describes consolidated resource requirement:

Table 3-3 Consolidated Resource Requirement per Site

Resource CPU Memory Ephemeral Storage(Gi) PVC
cnDBTier 93 189Gi 21Gi 1053Gi
SLF 162 120Gi 40Gi NA
ProvGw 32 32Gi 10Gi NA
Buffer 50 50Gi 20Gi 200Gi
Total 337 391Gi 91Gi 1253Gi
The following table provides cnDBTier resources:

Table 3-4 cnDBTier Resources

Micro Service Name Container Name Number of Pods CPU Allocation Per Pod Memory Allocation Per Pod Ephemeral Storage Per Pod PVC Allocation Per Pod Total Resources
Management node (ndbmgmd) mysqlndbcluster 2 2 CPUs 9 Gi 1 Gi 16 Gi

4 CPUs

18 Gi Memory

PVC: 32 Gi

Ephemeral Storage: 2 Gi

Data node (ndbmtd) mysqlndbcluster 4 4 CPUs 15 Gi 1 Gi 23 Gi (Backup: 12 Gi)

16 CPUs

60 Gi Memory

PVC: 140 Gi

Ephemeral Storage: 4 Gi

Data memory :10Gi
APP SQL node (ndbappmysqld) mysqlndbcluster 4 8 CPUs 10 Gi 1 Gi 20 Gi

32 CPUs

40 Gi Memory

PVC: 80 Gi

Ephemeral Storage: 4 Gi

SQL node (Used for Replication) (ndbmysqld) mysqlndbcluster 6 4 CPUs 10 Gi 1 Gi 125 Gi

24 CPUs

60 Gi Memory

PVC: 750 Gi

Ephemeral Storage: 6 Gi

DB Monitor Service (db-monitor-svc) db-monitor-svc 1 4 CPUs 4 Gi 1 Gi N/A

4 CPUs

4 Gi Memory

Ephemeral Storage: 1 Gi

DB Backup Manager Service (backup-manager-svc) backup-manager-svc 1 100m CPU 128 MB 1 Gi N/A

100m CPU

128 MB Memory

Ephemeral Storage: 1 Gi

Replication Service (Multi-site Leader) (db-replication-svc) db-replication-svc 1 8 CPUs 2 Gi 1 Gi 51 Gi

8 CPUs

2 Gi Memory

PVC: 51 Gi

Ephemeral Storage: 1 Gi

Replication Service (Multi-site Non-Leader) (db-replication-svc) db-replication-svc 2 2 CPUs 2 Gi 1 Gi N/A

4 CPUs

4 Gi Memory

Ephemeral Storage: 2 Gi

The following table describes SLF resources:

Table 3-5 SLF Resources

Microservice Name Container Name Number of Pods CPU Allocation Per Pod Memory Allocation Per Pod Total Resources UDR
Ingress-gateway-sig ingressgateway-sig 11 6 CPUs 4Gi

66 CPUs

44Gi

Ephemeral Storage: 11Gi

Ingress-gateway-prov ingressgateway-prov 2 4 CPUs 4Gi

8 CPUs

8Gi

Ephemeral Storage: 2Gi

Nudr-dr-service nudr-drservice 10 6 CPUs 4Gi

60 CPUs

40Gi

Ephemeral Storage: 10Gi

Nudr-dr-provservice nudr-dr-provservice 2 4 CPUs 4Gi

8 CPUs

8Gi

Ephemeral Storage: 2Gi

Nudr-nrf-client-nfmanagement nrf-client-nfmanagement 2 1 CPU 1Gi

2 CPUs

2Gi

Ephemeral Storage: 2Gi

Nudr-egress-gateway egressgateway 2 1 CPU 1Gi

2 CPUs

2Gi

Ephemeral Storage: 2Gi

Nudr-config nudr-config 2 2 CPUs 2Gi

4 CPUs

4Gi

Ephemeral Storage: 2Gi

Nudr-config-server nudr-config-server 2 2 CPUs 2Gi

4 CPUs

4Gi

Ephemeral Storage: 2Gi

alternate-route alternate-route 2 1 CPU 1Gi

2 CPUs

2Gi

Ephemeral Storage: 2Gi

app-info app-info 2 1 CPU 1Gi

2 CPUs

2Gi

Ephemeral Storage: 2Gi

perf-info perf-info 2 1 CPU 1Gi

2 CPUs

2Gi

Ephemeral Storage: 2Gi

Nudr-dbcr-auditor nudr-dbcr-auditor-service 1 2 CPUs 2Gi

2 CPUs

2Gi

Ephemeral Storage: 1Gi

Note:

The same resources and usage are used for all sites.

Table 3-6 Provisioning Gateway Resources

Microservice Name Container Name Number of Pods CPU Allocation Per Pod Memory Allocation Per Pod Total Resources
provgw-ingress-gateway ingressgateway 2 4 CPUs 4Gi

8 CPUs

8Gi Memory

Ephemeral Storage: 2Gi

provgw-egress-gateway egressgateway 2 4 CPUs 4Gi

8 CPUs

8Gi Memory

Ephemeral Storage: 2Gi

provgw-service provgw-service 2 4 CPUs 4Gi

8 CPUs

8Gi Memory

Ephemeral Storage: 2Gi

provgw-config provgw-config 2 2 CPUs 2Gi

4 CPUs

4Gi Memory

Ephemeral Storage: 2Gi

provgw-config-server provgw-config-server 2 2 CPUs 2Gi

4 CPUs

4Gi Memory

Ephemeral Storage: 2Gi

provgw-auditor-service auditor-service 1 2 CPUs 2Gi

2 CPUs

2Gi Memory

Ephemeral Storage: 1Gi

The following table provides observation data for the performance test that can be used for the benchmark testing to scale up SLF performance:

Table 3-7 Result and Observation

Parameter Values
TPS Achieved 34K SLF Lookup + 1.44K Provisioning
Success Rate 100%
Average SLF processing time for signaling requests 24ms
Average SLF processing time for provisioning requests 15ms

3.2 Test Scenario 2: EIR 10K TPS and 10k Diameter S13 Interface TPS (300 K Subscribers)

This test scenario describes performance and capacity improvements of EIR functionality offered by UDR and provides the benchmarking results for various deployment sizes.

The following features are enabled for this testcase:
  • Support for EIR International Mobile Equipment Identity Software Version (IMEISV) Fallback
  • Overload Handling
  • Ingress Gateway Pod Protection Using Rate Limiting
  • Diameter S13 Interface
  • International Mobile Subscriber Identity (IMSI) Fallback Lookup

EIR is benchmarked for compute and storage resources under the following conditions:

  • EIR Look Up: 20K
  • Total Subscribers: 300 K
  • Profile Size: 130 bytes

The following table describes the benchmarking parameters and their values:

Table 3-8 Traffic Model Details

Request Type Details TPS
EIR GET N17 GET Request 10K
ECR message Diameter S13 Interface ECR 10K

The following table describes the testcase parameters and their values:

Table 3-9 Testcase Parameters

Input Parameter Details Configuration Values
UDR Version Tag 25.2.201
Target TPS 10K EIR GET + 10K S13 EC
Traffic Profile 20K
The following table describes the consolidated resource requirements:

Table 3-10 Consolidated Resource Requirement per Site

Resource CPUs Memory Ephemeral Storage PVC
cnDBTier 56 141 Gi 16 Gi 516 Gi
EIR 141 97 Gi 34 Gi NA
Buffer 50 50 Gi 20 Gi 50 Gi
Total 247 288 Gi 70 Gi 566 Gi
The following table describes cnDBTier resources:

Table 3-11 cnDBtier Resources

Micro service name Container name Number of Pods CPU Allocation Per Pod Memory Allocation Per Pod PVC Allocation Per Pod Ephemeral Storage Per Pod Total Resources
Management node (ndbmgmd) mysqlndbcluster 2 2 CPUs 12 Gi 16 Gi 1 Gi

4 CPUs

24 Gi

Ephemeral Storage: 2 Gi

PVC: 32 Gi

Data node (ndbmtd) mysqlndbcluster 4 4 CPUs 20 Gi 28 Gi + backup: 56 Gi 1 Gi

16 CPUs

80 Gi

Ephemeral Storage: 4 Gi

PVC: 336 Gi

APP SQL node (ndbappmysqld) mysqlndbcluster 5 4 CPUs 4 Gi 10 Gi 1 Gi

20 CPUs

20 Gi

Ephemeral Storage: 5 Gi

PVC: 50 Gi

SQL node (Used for Replication) (ndbmysqld) mysqlndbcluster 2 4 CPUs 5 Gi 16 Gi 1 Gi

8 CPUs

10 Gi

Ephemeral Storage: 2 Gi

PVC: 32 Gi

DB Monitor Service (db-monitor-svc) db-monitor-svc 1 4 CPUs 4 Gi N/A 1 Gi

4 CPUs

4 Gi

Ephemeral Storage: 1 Gi

DB Backup Manager Service (backup-manager-svc) backup-manager-svc 1 1.1 CPU 1 Gi N/A 1 Gi

1.1 CPU

1 Gi

Ephemeral Storage: 1 Gi

Replication Service (db-replication-svc) db-replication-svc 1 2 CPU 2 Gi 66 Gi 1 Gi

2 CPUs

2 Gi

Ephemeral Storage: 1 Gi

PVC: 66 Gi

The following table describes EIR resources:

Table 3-12 EIR Resources

Micro service name Container name Number of Pods CPU Allocation Per Pod Memory Allocation Per Pod Ephemeral Storage Per Pod Total Resources
Ingress-gateway-sig ingressgateway-sig 4 6 CPUs 4 Gi 1 Gi

24 CPUs

16 Gi

Ephemeral Storage: 4 Gi

Ingress-gateway-prov ingressgateway-prov 2 4 CPUs 4 Gi 1 Gi

8 CPUs

8 Gi

Ephemeral Storage: 2 Gi

Nudr-dr-service nudr-drservice 3 6 CPUs 4 Gi 1 Gi

18 CPUs

12 Gi

Ephemeral Storage: 3 Gi

Nudr-dr-provservice nudr-dr-provservice 2 4 CPUs 4 Gi 1 Gi

8 CPUs

8 Gi

Ephemeral Storage: 2 Gi

Nudr-diam-gateway nudr-diam-gateway 2 6 CPUs 4 Gi 1 Gi

12 CPUs

8 Gi

Ephemeral Storage: 2 Gi

Nudr-diameterproxy nudr-diameterproxy 8 6 CPUs 4 Gi 1 Gi

48 CPUs

32 Gi

Ephemeral Storage: 8 Gi

Nudr-config nudr-config 2 1 CPU 1 Gi 1 Gi

2 CPUs

2 Gi

Ephemeral Storage: 2 Gi

Nudr-config-server nudr-config-server 2 1 CPU 1 Gi 1 Gi

2 CPUs

2 Gi

Ephemeral Storage: 2 Gi

Alternate-route alternate-route 2 2 CPUs 2 Gi 1 Gi

4 CPUs

4 Gi

Ephemeral Storage: 2 Gi

Nudr-nrf-client-nfmanagement-service nrf-client-nfmanagement 2 1 CPU 1 Gi 1 Gi

2 CPUs

2 Gi

Ephemeral Storage: 2 Gi

App-info app-info 2 1 CPU 1 Gi 1 Gi

2 CPUs

2 Gi

Ephemeral Storage: 2 Gi

Perf-info perf-info 2 1 CPU 1 Gi 1 Gi

2 CPUs

2 Gi

Ephemeral Storage: 2 Gi

Nudr-dbcr-auditor-service nudr-dbcr-auditor-service 1 2 CPUs 2 Gi 1 Gi

2 CPUs

2 Gi

Ephemeral Storage: 1 Gi

The following table provides observation data for the performance test that can be used for the benchmark testing to scale up EIR performance:

Table 3-13 Result and Observation

Parameter Values
TPS Achieved 20K
Success Rate 100%
Average EIR processing time (Request and Response) 9 ms
EIR Response Timeout 2.7s
N17 Latency: 6 ms
S13 Latency 7 ms

3.3 Test Scenario 3: UDR Call Model: 25K N36 300 Notifications and 600 Provisioning (SOAP) Profile (40M Subscribers)

You can perform benchmark tests on UDR for compute and storage resources by considering the following conditions:

  • Signaling: 25K TPS
  • Provisioning: 600 TPS
  • Total Subscribers: 40 Million
The following features are enabled for this testcase:
  • Auto Enrollment and Auto Create Features
  • Overload Handling
  • ETag (Entity Tag)
  • Ingress Gateway Pod Protection Using Rate Limiting
  • Support for User-Agent Header
  • 3gpp-Sbi-Correlation-Info Header
  • Suppress Notification
  • Support for Post Operation for an Existing Subscription
  • Subscriber Activity Logging

The following table describes the benchmarking parameters and their values:

Table 3-14 Traffic Model Details

Request Type Details TPS
N36 traffic 25K TPS subs-to-notify POST 5K (20%)
sm-data GET 5K (20%)
subs-to-notify DELETE 5K (20%
sm-data PATCH 10K (40%)
SOAP PROVISIONING 600 TPS GET 100
UPDATE QUOTA 50
UPDATE DYNAMIC QUOTA 50
UPDATE STATE 100
UPDATE SUBSCRIBER 100
CREATE SUBSCRIBER 100
DELETE SUBSCRIBER 100
The following table describes the test case parameters and their values:

Table 3-15 Testcase Parameters

Input Parameter Details Configuration Values
UDR Version Tag 25.2.201
Target TPS 25K TPS Signaling + 600 SOAP
Notification Rate 300

Table 3-16 Consolidated Resource Requirement per Site

Resource CPU Memory Ephemeral Storage PVC
cnDBTier 164 CPUs 643 Gi 29 Gi 2070 Gi
UDR 270 CPUs 192 Gi 57 Gi NA
PROVGW 28 28 10 NA
Buffer 50 CPUs 50 Gi 20 Gi 200 Gi
Total 519 CPUs 913 Gi 116 Gi 2270 Gi

The following table describes cnDBTier resources:

Table 3-17 cnDBTier Resources

Micro service name Container name Number of Pods CPU Allocation Per Pod Memory Allocation Per Pod Ephemeral Storage Per Pod PVC Allocation Per Pod Total Resources
Management node (ndbmgmd) mysqlndbcluster 2 2 CPUs 10 Gi 1 Gi 15 Gi

4 CPUs

20 Gi

Ephemeral Storage: 2 Gi

PVC: 30 Gi

Data node (ndbmtd) mysqlndbcluster 4 9 CPUs 124 Gi 1 Gi 134 Gi

36 CPUs

496 Gi

Ephemeral Storage: 4 Gi

PVC: 1416 Gi

APP SQL node (ndbappmysqld) mysqlndbcluster 18 6 CPUs 4 Gi 1 Gi 8 Gi

108 CPUs

72 Gi

Ephemeral Storage: 18 Gi

PVC: 144 Gi

SQL node (Used for Replication) (ndbmysqld) mysqlndbcluster 2 4 CPUs 24 Gi 1 Gi 110 Gi

8 CPUs

48 Gi

Ephemeral Storage: 2 Gi

PVC: 220 Gi

DB Monitor Service (db-monitor-svc) db-monitor-svc 1 4 CPUs 4 Gi 1 Gi NA

4 CPUs

4 Gi

Ephemeral Storage: 1 Gi

DB Backup Manager Service (backup-manager-svc) backup-manager-svc 1 1 CPU 1 Gi 1 Gi NA

1 CPU

1 Gi

Ephemeral Storage: 1 Gi

Replication service (Multi site cases) replication-svc 1 2 CPUs 2 Gi 1 Gi 260 Gi

2 CPUs

2 Gi

Ephemeral Storage: 1 Gi

PVC: 260 Gi

The following table describes UDR resources:

Table 3-18 UDR Resources

Micro service name Container name Number of Pods CPU Allocation Per Pod Memory Allocation Per Pod Ephemeral Storage Per Pod Total Resources
Ingress-gateway-sig ingressgateway-sig 13 6 CPUs 4 Gi 1 Gi

78 CPUs

52 Gi

Ephemeral Storage: 13 Gi

Ingress-gateway-prov ingressgateway-prov 2 4 CPUs 4 Gi 1 Gi

8 CPUs

8 Gi

Ephemeral Storage: 2 Gi

Nudr-dr-service nudr-drservice 21 6 CPUs 4 Gi 1 Gi

126 CPUs

84 Gi

Ephemeral Storage: 21 Gi

Nudr-dr-provservice nudr-dr-provservice 3 4 CPUs 4 Gi 1 Gi

12 CPUs

12 Gi

Ephemeral Storage: 3 Gi

Nudr-notify-service nudr-notify-service 3 6 CPUs 5 Gi 1 Gi

18 CPUs

15 Gi

Ephemeral Storage: 3 Gi

Nudr-egress-gateway egressgateway 2 6 CPUs 4 Gi 1 Gi

12 CPUs

8 Gi

Ephemeral Storage: 2 Gi

Nudr-config nudr-config 2 1 CPUs 1 Gi 1 Gi

2 CPUs

2 Gi

Ephemeral Storage: 2 Gi

Nudr-config-server nudr-config-server 2 1 CPUs 1 Gi 1 Gi

2 CPUs

2 Gi

Ephemeral Storage: 2 Gi

Alternate-route alternate-route 2 2 CPUs 2 Gi 1 Gi

4 CPUs

4 Gi

Ephemeral Storage: 2 Gi

Nudr-nrf-client-nfmanagement-service nrf-client-nfmanagement 2 1 CPUs 1 Gi 1 Gi

2 CPUs

2 Gi

Ephemeral Storage: 2 Gi

App-info app-info 2 1 CPUs 1 Gi 1 Gi

2 CPUs

2 Gi

Ephemeral Storage: 2 Gi

Perf-info perf-info 2 1 CPUs 1 Gi 1 Gi

2 CPUs

2 Gi

Ephemeral Storage: 2 Gi

Nudr-dbcr-auditor-service nudr-dbcr-auditor-service 1 2 CPUs 1 Gi 1 Gi

2 CPUs

2 Gi

Ephemeral Storage: 1 Gi

The following table describes Provisioning Gateway resources:

Table 3-19 Provisioning Gateway Resources

Micro service name Container name Number of Pods CPU Allocation Per Pod Memory Allocation Per Pod Ephemeral Storage Per Pod Total Resources
provgw-ingress-gateway ingressgateway 2 4 CPUs 4 Gi 1 Gi

8 CPUs

8 Gi Memory

Ephemeral Storage: 2 Gi

provgw-egress-gateway egressgateway 2 4 CPUs 4 Gi 1 Gi

8 CPUs

8 Gi Memory

Ephemeral Storage: 2 Gi

provgw-service provgw-service 4 2 CPUs 2 Gi 1 Gi

8 CPUs

8 Gi Memory

Ephemeral Storage: 4 Gi

provgw-config provgw-config 2 2 CPUs 2 Gi 1 Gi

4 CPUs

4 Gi Memory

Ephemeral Storage: 2 Gi

The following table provides observation data for the performance test that can be used for the benchmark testing to scale up UDR performance:

Table 3-20 Result and Observation

Parameter Values
TPS Achieved 25K Signaling + 600
UDR Request Average Latency 30ms
Success rate 100%
UDR Response Timeout 2.7s
Signaling Requests Latency Recorded 24ms
Provisioning Requests Latency Recorded 38ms

3.4 Test Scenario 4: UDR Call Model: 17.2K N36 + 10K SH+1.2K Notifications and 600 Provisioning (SOAP) Profile (40M Subscribers)

You can perform benchmark tests on UDR for compute and storage resources by considering the following conditions:

  • Signaling : 17.2K N36 + 10K SH
  • Provisioning: 600 TPS
  • Total Subscribers: 40 Million
The following features are enabled for this testcase:
  • Auto Enrollment and Auto Create Features
  • Overload Handling
  • ETag (Entity Tag)
  • Ingress Gateway Pod Protection Using Rate Limiting
  • Support for User-Agent Header
  • 3gpp-Sbi-Correlation-Info Header
  • Suppress Notification
  • Subscriber Activity Logging
  • Diameter Gateway Pod Congestion Control
  • Support for Post Operation for an Existing Subscription

The following table describes the benchmarking parameters and their values:

Table 3-21 Traffic Model Details

Request Type Details TPS
N36 17.2K TPS subs-to-notify POST 3.44K (20%)
sm-data GET 3.44K (20%)
subs-to-notify DELETE 3.44K (20%)
sm-data PATCH 6.88K (40%)
SH 10K TPS UDR 4K
PUR 1.2K
SNR 4.8K
SOAP PROVISIONING 600 TPS GET 100
UPDATE QUOTA 50
UPDATE DYNAMIC QUOTA 50
UPDATE STATE 100
UPDATE SUBSCRIBER 100
CREATE SUBSCRIBER 100
DELETE SUBSCRIBER 100
The following table describes the test case parameters and their values:

Table 3-22 Testcase Parameters

Input Parameter Details Configuration Values
UDR Version Tag 25.2.201
Target TPS 17.2K N36 + 10K SH + 600 SOAP
Notification Rate 1.2K

Table 3-23 Consolidated Resource Requirement per Site

Resource CPU Memory Ephemeral Storage PVC
cnDBTier 155 CPUs 642 Gi 25 Gi 2038 Gi
UDR 288 CPUs 206 Gi 60 Gi NA
PROVGW 28 CPUs 28 Gi 10 Gi NA
Buffer 50 CPUs 50 Gi 20 Gi 200 Gi
Total 528 CPUs 926 Gi 115 Gi 2238 Gi
The following table describes cnDBTier resources:

Table 3-24 cnDBTier Resources

Micro service name Container name Number of Pods CPU Allocation Per Pod Memory Allocation Per Pod Ephemeral Storage Per Pod PVC Allocation Per Pod Total Resources
Management node (ndbmgmd) mysqlndbcluster 2 2 CPUs 10 Gi 1 Gi 15 Gi

4.5 CPUs

21 Gi

Ephemeral Storage: 2 Gi

PVC: 30 Gi
db-infra-monitor-svc 200m CPU 256 MB
Data node (ndbmtd) mysqlndbcluster 4 9 CPUs 124 Gi 1 Gi 134 Gi (backup: 220 Gi)

45 CPUs

501 Gi

Ephemeral Storage: 4 Gi

PVC: 1416 Gi
db-infra-monitor-svc 200m CPU 256 MB
db-backup-executor-svc 2 CPU 1 Gi
APP SQL node (ndbappmysqld) mysqlndbcluster 14 6 CPUs 4 Gi 1 Gi 8 Gi

89 CPUs

63 Gi

Ephemeral Storage: 14 Gi

PVC: 112 Gi
db-infra-monitor-svc 200m CPU 256 MB
init-sidecar 100m CPU 256 MB
SQL node (Used for Replication) (ndbmysqld) mysqlndbcluster 2 4 CPUs 24 Gi 1 Gi 110 Gi

9 CPUs

49 Gi

Ephemeral Storage: 2 Gi

PVC: 220 Gi
db-infra-monitor-svc 200m CPU 256 MB
init-sidecar 100m CPU 256 MB
DB Monitor Service (db-monitor-svc) db-monitor-svc 1 4 CPUs 4 Gi 1 Gi NA

4 CPUs

4 Gi

Ephemeral Storage: 1 Gi
DB Backup Manager Service (backup-manager-svc) backup-manager-svc 1 1 CPU 1 Gi 1 Gi NA

1 CPU

1 Gi

Ephemeral Storage: 1 Gi
Replication service (Multi site cases) replication-svc 1 2 CPUs 2 Gi 1 Gi 260 Gi

2.1 CPUs

2.3 Gi

Ephemeral Storage: 1 Gi

PVC: 260 Gi
init-discover-sql-ips 100m CPU 256 MB
The following table describes UDR resources:

Table 3-25 UDR Resources

Micro service name Container name Number of Pods CPU Allocation Per Pod Memory Allocation Per Pod Ephemeral Storage Per Pod Total Resources
Ingress-gateway-sig ingressgateway-sig 9 6 CPUs 4 Gi 1 Gi

54 CPUs

36 Gi

Ephemeral Storage: 9 Gi

Ingress-gateway-prov ingressgateway-prov 2 4 CPUs 4 Gi 1 Gi

8 CPUs

8 Gi

Ephemeral Storage: 2 Gi

Nudr-dr-service nudr-drservice 17 6 CPUs 4 Gi 1 Gi

102 CPUs

68 Gi

Ephemeral Storage: 17 Gi

Nudr-dr-provservice nudr-dr-provservice 3 4 CPUs 4 Gi 1 Gi

12 CPUs

12 Gi

Ephemeral Storage: 3 Gi

Nudr-notify-service nudr-notify-service 3 6 CPUs 5 Gi 1 Gi

18 CPUs

15 Gi

Ephemeral Storage: 3 Gi

Nudr-egress-gateway egressgateway 2 6 CPUs 4 Gi 1 Gi

12 CPUs

8 Gi

Ephemeral Storage: 2 Gi

Nudr-diam-gateway nudr-diam-gateway 2 6 CPUs 5 Gi 1 Gi

12 CPUs

10 Gi

Ephemeral Storage: 2 Gi

Nudr-diameterproxy nudr-diameterproxy 9 6 CPUs 4 Gi 1 Gi

54 CPUs

36 Gi

Ephemeral Storage: 9 Gi

Nudr-config nudr-config 2 1 CPU 1 Gi 1 Gi

2 CPUs

2 Gi

Ephemeral Storage: 2 Gi

Nudr-config-server nudr-config-server 2 1 CPU 1 Gi 1 Gi

2 CPUs

2 Gi

Ephemeral Storage: 2 Gi

Alternate-route alternate-route 2 2 CPUs 2 Gi 1 Gi

4 CPUs

4 Gi

Ephemeral Storage: 2 Gi

Nudr-nrf-client-nfmanagement-service nrf-client-nfmanagement 2 1 CPU 1 Gi 1 Gi

2 CPUs

2 Gi

Ephemeral Storage: 2 Gi

App-info app-info 2 1 CPU 1 Gi 1 Gi

2 CPUs

2 Gi

Ephemeral Storage: 2 Gi

Perf-info perf-info 2 1 CPU 1 Gi 1 Gi

2 CPUs

2 Gi

Ephemeral Storage: 2 Gi

Nudr-dbcr-auditor-service nudr-dbcr-auditor-service 1 2 CPUs 2 Gi 1 Gi

2 CPUs

2 Gi

Ephemeral Storage: 1 Gi

The following table describes Provisioning Gateway resources:

Table 3-26 Provisioning Gateway Resources

Micro service name Container name Number of Pods CPU Allocation Per Pod Memory Allocation Per Pod Ephemeral Storage Per Pod Total Resources
provgw-ingress-gateway ingressgateway 2 4 CPUs 4 Gi 1 Gi

8 CPUs

8 Gi Memory

Ephemeral Storage: 2 Gi

provgw-egress-gateway egressgateway 2 4 CPUs 4 Gi 1 Gi

8 CPUs

8 Gi Memory

Ephemeral Storage: 2 Gi

provgw-service provgw-service 4 2 CPUs 2 Gi 1 Gi

8 CPUs

8 Gi Memory

Ephemeral Storage: 4 Gi

provgw-config provgw-config 2 2 CPUs 2 Gi 1 Gi

4 CPUs

4 Gi Memory

Ephemeral Storage: 2 Gi

The following table provides observation data for the performance test that can be used for the benchmark testing to scale up UDR performance:

Table 3-27 Result and Observation

Parameter Values
TPS Achieved 17.2K N36 + 10K SH + 600
UDR Request Average Latency 31ms
Success rate 100%
UDR Response Timeout 2.7s
Signaling Requests Latency Recorded 31ms
Provisioning Requests Latency Recorded 45ms
Diameter (SH) Requests Latency Recorded 18ms