UDR Benchmark Testing

3 UDR Benchmark Testing

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

3.1 Test Scenario 1: SLF Call Deployment Model

This section provides information about SLF call deployment model test scenarios.

3.1.1 SLF Call Model: 34K TPS and 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.

The following features are enabled for this testcase:

Support for Default Group ID in SLF
Oauth2.0
Subscriber Activity Logging
Support for LCI and OCI Header
Overload Handling
Support for User-Agent Header
Alternate Route Service

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

Signaling (SLF Look Up): 34K TPS
Provisioning: 1.44K TPS
Total Subscribers: 50M

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 Provisioning Gateway one site)	CREATE	144
	DELETE	144
	UPDATE	576
	GET	576

The following table describes the testcase parameters and their values:

Table 3-2 Testcase Parameters

Input Parameter Details	Configuration Values
UDR Version Tag	24.3.0
Target TPS	34K Lookup + 1.44K Provisioning
Traffic Profile	SLF 34K Profile
UDR Response Timeout	2.7s
Client Timeout	10s
Signaling Requests Latency Recorded on Client	17ms
Provisioning Requests Latency Recorded on Client	45ms

The following table describes consolidated resource requirement and their utilization:

Table 3-3 Consolidated Resource Requirement

Resource	CPU	Memory	Ephemeral Storage	PVC
cnDBTier	134	495 GB	22 GB	640 GB
SLF	247	152 GB	38 GB	NA
ProvGw	32	30 GB	10 GB	NA
Buffer	50	50 GB	20 GB	200 GB
Total	463	727 GB	90 GB	840 GB

Note:

All values are inclusive of ASM sidecar.

The following table describes cnDBTier1 resources and their utilization:

Note:

The same resources and usage are application for cnDBTier2
For cnDBTier, you must use ocudr_slf_37msub_dbtier and ocudr_udr_10msub_dbtier custom value files for SLF and UDR respectively. For more information, see Cloud Native Core, Unified Data Repository Installation, Upgrade, and Fault Recovery Guide.

Table 3-4 cnDBTier Resources and Usage

Microservice Name	Container Name	Number of Pods	CPU Allocation Per Pod (cnDBtier1)	Memory Allocation Per Pod (cnDBtier1)	Ephemeral Storage Per Pod	PVC Allocation Per Pod	Total Resources (cnDBtier)	CPU Usage (cnDBtier)	Memory Usage
Management node (ndbmgmd)	mysqlndbcluster	2	2 CPUs	9 GB	1 GB	16 GB	6 CPUs 26 GB Ephemeral Storage: 2 GB PVC Allocation: 32 GB	Minimal resources are used
Management node (ndbmgmd)		2	1 CPUs	4 GB	1 GB	16 GB		Minimal resources are used
Data node (ndbmtd)	mysqlndbcluster	6	4 CPUs	50 GB	1 GB	25 GB (Backup: 56 GB)	42 CPUs 336 GB Ephemeral Storage: 6 GB PVC Allocation: 486 GB Data Memory: 25 GB	3.5 CPU/pod	30 GB/pod
	istio-proxy		2 CPUs	4 GB
	db-backup-executor-svc		1 CPU	1 GB
APP SQL node (ndbappmysqld)	mysqlndbcluster	9	4 CPUs	4 GB	1 GB	10 GB	63 CPUs 72 GB Ephemeral Storage: 9 GB PVC Allocation: 90 GB	4 CPU/pod	1 GB/pod
APP SQL node (ndbappmysqld)	istio-proxy	9	3 CPUs	4 GB	1 GB	10 GB		4 CPU/pod	1 GB/pod
SQL node (Used for Replication) (ndbmysqld)	mysqlndbcluster	2	4 CPUs	16 GB	1 GB	16 GB	13 CPUs 41 GB Ephemeral Storage: 2 GB PVC Allocation: 32 GB	Minimal resources are used
	istio-proxy		2 CPUs	4 GB	1 GB	16 GB
	init-sidecar		100m CPU	256 MB
DB Monitor Service (db-monitor-svc)	db-monitor-svc	1	4 CPUs	4 GB	1 GB	NA	5 CPUs 5 GB Ephemeral Storage: 1 GB	Minimal resources are used
DB Monitor Service (db-monitor-svc)	istio-proxy	1	1 CPUs	1 GB	1 GB	NA	5 CPUs 5 GB Ephemeral Storage: 1 GB	Minimal resources are used
DB Backup Manager Service (backup-manager-svc)	backup-manager-svc	1	100m CPU	128 MB	1 GB	NA	2 CPUs 2 GB Ephemeral Storage: 1 GB	Minimal resources are used
DB Backup Manager Service (backup-manager-svc)	istio-proxy	1	1 CPU	1 GB	1 GB	NA	2 CPUs 2 GB Ephemeral Storage: 1 GB	Minimal resources are used
Replication Service (db-replication-svc)	db-replication-svc	1	2 CPU	2 GB	1 GB	NA	3 CPUs 13 GB Ephemeral Storage: 1 GB	Minimal resources are used
Replication Service (db-replication-svc)	istio-proxy	1	200m CPU	500MB	1 GB	NA	3 CPUs 13 GB Ephemeral Storage: 1 GB	Minimal resources are used

Additional cnDBTier configuration are as follows:

ndb:
  annotations:
    - sidecar.istio.io/inject: "true"
    - proxy.istio.io/config: "{concurrency: 8}"
    - sidecar.istio.io/proxyCPU: "2000m"
    - sidecar.istio.io/proxyCPULimit: "2000m"
    - sidecar.istio.io/proxyMemory: "4Gi"
    - sidecar.istio.io/proxyMemoryLimit: "4Gi"

mgm:
  annotations:
    - sidecar.istio.io/inject: "true"
    - proxy.istio.io/config: "{concurrency: 8}"
    - sidecar.istio.io/proxyCPU: "1000m"
    - sidecar.istio.io/proxyCPULimit: "1000m"
    - sidecar.istio.io/proxyMemory: "4Gi"
    - sidecar.istio.io/proxyMemoryLimit: "4Gi"
 
api:
  annotations:
    - sidecar.istio.io/inject: "true"
    - proxy.istio.io/config: "{concurrency: 8}"
    - sidecar.istio.io/proxyCPU: "2000m"
    - sidecar.istio.io/proxyCPULimit: "2000m"
    - sidecar.istio.io/proxyMemory: "4Gi"
    - sidecar.istio.io/proxyMemoryLimit: "4Gi"
  ndbapp:
    annotations:
      - sidecar.istio.io/inject: "true"
      - proxy.istio.io/config: "{concurrency: 8}"
      - sidecar.istio.io/proxyCPU: "3000m"
      - sidecar.istio.io/proxyCPULimit: "3000m"
      - sidecar.istio.io/proxyMemory: "4Gi"
      - sidecar.istio.io/proxyMemoryLimit: "4Gi"

The following table describes SLF resources and their utilization for Site1 (Lookup Latency: 10ms):

Table 3-5 SLF Resources and Usage

Microservice name	Container name	Number of Pods	CPU Allocation Per Pod	Memory Allocation Per Pod	Total Resources	CPU Usage	Memory Usage	CPU Utilization hpa
Ingress-gateway-sig	ingressgateway-sig	11	6 CPUs	4 GB	110 CPUs 55 GB Memory Ephemeral Storage: 11 GB	3.7 CPU/pod	2.1 GB/pod	64%
Ingress-gateway-sig	istio-proxy	11	4 CPUs	1 GB	110 CPUs 55 GB Memory Ephemeral Storage: 11 GB	2.8 CPU/pod	350 MB/pod	64%
Ingress-gateway-prov	ingressgateway-prov	2	4 CPUs	4 GB	12 CPUs 10 GB Ephemeral Storage: 2 GB	1 CPU/pod	1.4 GB/pod	25%
Ingress-gateway-prov	istio-proxy	2	2 CPUs	1 GB	12 CPUs 10 GB Ephemeral Storage: 2 GB	0.8 CPU/pod	250 MB/pod	25%
Nudr-dr-service	nudr-drservice	9	6 CPUs	4 GB	81 CPUs 45 GB Ephemeral Storage: 9 GB	3.4 CPU/pod	1.7 GB/pod	61%
Nudr-dr-service	istio-proxy	9	3 CPUs	1 GB	81 CPUs 45 GB Ephemeral Storage: 9 GB	2.4 CPU/pod	270 MB/pod	61%
Nudr-dr-provservice	nudr-dr-provservice	2	4 CPUs	4 GB	12 CPUs 10 GB Ephemeral Storage: 2 GB	1.6 CPU/pod	1.5 GB/pod	32%
Nudr-dr-provservice	istio-proxy	2	2 CPUs	1 GB	12 CPUs 10 GB Ephemeral Storage: 2 GB	0.7 CPU/pod	270 MB/pod	32%
Nudr-nrf-client-nfmanagement	nrf-client-nfmanagement	2	1 CPU	1 GB	4 CPUs 4 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Nudr-nrf-client-nfmanagement	istio-proxy	2	1 CPUs	1 GB	4 CPUs 4 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Nudr-egress-gateway	egressgateway	2	1 CPUs	1 GB	4 CPUs 4 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Nudr-egress-gateway	istio-proxy	2	1 CPUs	1 GB	4 CPUs 4 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Nudr-config	nudr-config	2	2 CPUs	2 GB	6 CPUs 6 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Nudr-config	istio-proxy	2	1 CPUs	1 GB	6 CPUs 6 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Nudr-config-server	nudr-config-server	2	2 CPUs	2 GB	6 CPUs 6 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Nudr-config-server	istio-proxy	2	1 CPUs	1 GB	6 CPUs 6 GB Ephemeral Storage: 2 GB	Minimal resources are used.
alternate-route	alternate-route	2	1 CPUs	1 GB	4 CPUs 4 GB Ephemeral Storage: 2 GB	Minimal resources are used.
alternate-route	istio-proxy	2	1 CPUs	1 GB	4 CPUs 4 GB Ephemeral Storage: 2 GB	Minimal resources are used.
app-info	app-info	2	1 CPUs	1 GB	4 CPUs 4 GB Ephemeral Storage: 2 GB	Minimal resources are used.
app-info	istio-proxy	2	1 CPUs	1 GB	4 CPUs 4 GB Ephemeral Storage: 2 GB	Minimal resources are used.
perf-info	perf-info	2	1 CPUs	1 GB	4 CPUs 4 GB Ephemeral Storage: 2 GB	Minimal resources are used.
perf-info	istio-proxy	2	1 CPUs	1 GB	4 CPUs 4 GB Ephemeral Storage: 2 GB	Minimal resources are used.

Note:

The same resources and usage are used for Site2.

The following table describes provision gateway resources and their utilization (Provisioning Latency: 30ms):

Table 3-6 Provision Gateway Resources and their utilization

Microservice name	Container name	Number of Pods	CPU Allocation Per Pod	Memory Allocation Per Pod	Total Resources	CPU Usage	Memory Usage	CPU Utilization hpa
provgw-ingress-gateway	ingressgateway	2	2 CPUs	2 GB	6 CPUs 6 GB Memory Ephemeral Storage: 2 GB	1.1 CPU/pod	1.5 GB/pod	61%
provgw-ingress-gateway	istio-proxy	2	1 CPUs	1 GB	6 CPUs 6 GB Memory Ephemeral Storage: 2 GB	0.8 CPU/pod	285 MB/pod	61%
provgw-egress-gateway	egressgateway	2	3 CPUs	2 GB	6 CPUs 6 GB Memory Ephemeral Storage: 2 GB	1 CPU/pod	1.1 GB/pod	60%
provgw-egress-gateway	istio-proxy	2	1 CPUs	1 GB	6 CPUs 6 GB Memory Ephemeral Storage: 2 GB	0.6 CPU/pod	300 MB/pod	60%
provgw-service	provgw-service	2	3 CPUs	2 GB	8 CPUs 6 GB Memory Ephemeral Storage: 2 GB	1.2 CPU/pod	1.2 GB/pod	49%
provgw-service	istio-proxy	2	1 CPUs	1 GB	8 CPUs 6 GB Memory Ephemeral Storage: 2 GB	0.75 CPU/pod	255 MB/pod	49%
provgw-config	provgw-config	2	2 CPUs	2 GB	6 CPUs 6 GB Memory Ephemeral Storage: 2 GB	Minimal resources are used. Utilization data is not captured.
provgw-config	istio-proxy	2	1 CPUs	1 GB	6 CPUs 6 GB Memory Ephemeral Storage: 2 GB
provgw-config-server	provgw-config-server	2	2 CPUs	2 GB	6 CPUs 6 GB Memory Ephemeral Storage: 2 GB	Minimal resources are used. Utilization data is not captured.
provgw-config-server	istio-proxy	2	1 CPUs	1 GB	6 CPUs 6 GB Memory Ephemeral Storage: 2 GB

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
Test Duration	24hr
TPS Achieved	34K SLF Lookup + 1.44k Provisioning
Success Rate	100%
Average SLF processing time (Request and Response)	26ms

3.2 Test Scenario 2: EIR 10k TPS and 10k Diameter S13 Interface TPS

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:

Overload Handling
Ingress Gateway Pod Protection
Network Policy
Diameter Gateway Pod Congestion Control

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

EIR Look Up: 20k
Total Subscribers: 1M
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	24.3.0
Target TPS	20k Lookup
Traffic Profile	20k
EIR Response Timeout	2.7s
Client Timeout	10s
N17 Latency:	6.2 ms
S13 Latency	11 ms

The following table describes cnDBTier resources and their utilization:

Table 3-10 cnDBTier Resources and their Utilization

Micro service name	Container name	Number of Pods	CPU Allocation Per Pod	Memory Allocation Per Pod (cnDBtier1)	Total Resources (cnDBtier1)	CPU Usage (cnDBtier1)	Memory Usage (cnDBtier1)
Management node	mysqlndbcluster	2	2 CPUs	11.25 GB	4 CPU 23 GB Memory Ephemeral Storage: 2 GB PVC Allocation: 32 GB	Minimal resources are used.
Data node	mysqlndbcluster	4	4 CPUs	33 GB	16 CPU 132 GB Memory Ephemeral Storage: 4 GB PVC Allocation: 324 GB	1.1 CPU/pod	20 GB/pod
APP SQL node	mysqlndbcluster	5	4 CPUs	4 GB	20 CPU 20 GB Memory Ephemeral Storage: 5 GB PVC Allocation: 50 GB	2.5 CPU/pod	650 GB/pod
SQL node (Used for Replication)	mysqlndbcluster	2	4 CPUs	16 GB	8 CPU 32 GB Memory Ephemeral Storage: 2 GB PVC Allocation: 32 GB	Minimal resources are used.
DB Monitor Service (db-monitor-svc)	db-monitor-svc	1	4 CPUs	4 GB	4 CPUs 4 GB Memory Ephemeral Storage: 1 GB	Minimal resources are used.
DB Backup Manager Service (backup-manager-svc)	backup-manager-svc	1	100m CPUs	128 MB	100m CPUs 128 MB Memory Ephemeral Storage: 1 GB	Minimal resources are used.
Replication Service (db-replication-svc)	db-replication-svc	1	2 CPU	2 GB	2 CPUs 2 MB Memory Ephemeral Storage: 1 GB	Minimal resources are used.

The following table describes EIR resources and their utilization:

Table 3-11 EIR Resources and their Utilization

Micro service name	Container name	Number of Pods	CPU Allocation Per Pod	Memory Allocation Per Pod	Ephemeral Storage Per Pod	Total Resources	CPU Usage	Memory Usage	CPU Utilization (HPA)
Ingress-gateway-sig	Ingress-gateway-sig	4	6 CPUs	4 GB	1 GB	24 CPUs 16 GB Memory Ephemeral Storage: 4 GB	2.5 CPU/pod	1.5 GB/pod	42%
Ingress-gateway-prov	Ingress-gateway-prov	2	4 CPUs	4 GB	1 GB	8 CPUs 8 GB Memory Ephemeral Storage: 2 GB	.09 CPU/pod	1.4 GB/pod	23%
Nudr-dr-service	nudr-drservice	3	6 CPUs	4 GB	1 GB	18 CPUs 12 GB Memory Ephemeral Storage: 3 GB	3.2 CPU/pod	1.7 GB/pod	52%
Nudr-dr-provservice	nudr-dr-provservice	2	4 CPUs	4 GB	1 GB	8 CPUs 8 GB Memory Ephemeral Storage: 2 GB	.9 CPU/pod	1.5 GB/pod	23%
Nudr-diam-gateway	nudr-diam-gateway	2	6 CPUs	4 GB	1 GB	12 CPUs 8 GB Memory Ephemeral Storage: 2 GB	1.1 CPU/pod	1.4 GB/Pod	18%
Nudr-diameterproxy	nudr-diameterproxy	8	6 CPUs	4 GB	1 GB	48 CPUs 32 GB Memory Ephemeral Storage: 8 GB	2.2 CPU/pod	1.6 GB/pod	33%
Nudr-config	nudr-config	2	1 CPUs	1 GB	1 GB	2 CPUs 2 GB Memory Ephemeral Storage: 2 GB	Minimal resources are used.
Nudr-config-server	nudr-config-server	2	1 CPUs	1 GB	1 GB	2 CPU 2 GB Memory Ephemeral Storage: 2 GB	Minimal resources are used.
Alternate-route	alternate-route	2	1 CPUs	1 GB	1 GB	2 CPU 2 GB Memory Ephemeral Storage: 2 GB	Minimal resources are used.
Nudr-nrf-client-nfmanagement-service	nrf-client-nfmanagement	2	1 CPUs	1 GB	1 GB	2 CPU 2 GB Memory Ephemeral Storage: 2 GB	Minimal resources are used.
App-info	app-info	2	1 CPUs	1 GB	1 GB	2 CPU 2 GB Memory Ephemeral Storage: 2 GB	Minimal resources are used.
Perf-info	perf-info	2	1 CPUs	1 GB	1 GB	2 CPU 2 GB Memory Ephemeral Storage: 2 GB	Minimal resources are used.
Nudr-dbcr-auditor-service	nudr-dbcr-auditor-service	1	1 CPUs	1 GB	1 GB	1 CPU 1 GB Memory Ephemeral Storage: 1 GB	Minimal resources are used.

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-12 Result and Observation

Parameter	Values
Test Duration	12hrs
TPS Achieved	20k
Success Rate	100%
Average EIR processing time (Request and Response)	9 ms

3.3 Test Scenario 3: SOAP and Diameter Deployment Model

2K SOAP provisioning TPS for ProvGw for Medium profile + Diameter 25K with Large profile

The following features are disabled for this testcase:

TLS
OAuth2.0
Header Validations like XFCC, server header, and user agent header

UDR is benchmarked for compute and storage resources under following conditions:

Signaling : 10K TPS
Provisioning: 2K TPS
Total Subscribers: 1M - 10M range used for Diameter Sh and 1M range used for SOAP/XML
Profile Size: 2.2KB
Average HTTP Provisioning Request Packet Size: NA
Average HTTP Provisioning Response Packet Size: NA

Figure 3-1 SOAP and Diameter Deployment Model

The following table describes the benchmarking parameters and their values:

Table 3-13 Traffic Model Details

Request Type	Details	TPS
Diameter SH Traffic	SH Traffic	25K
Provisioning (2K using Provgw)	SOAP Traffic	2K

Table 3-14 SOAP Traffic Model

Request Type	SOAP Traffic %
GET	33%
DELETE	11%
POST	11%
PUT	45%

Table 3-15 Diameter Traffic Model

Request Type	Diameter Traffic %
SNR	25%
PUR	50%
UDR	25%

The following table describes the benchmarking parameters and their values:

Table 3-16 Testcase Parameters

Input Parameter Details	Configuration Values
UDR Version Tag	22.2.0
Target TPS	25K + 2K
Traffic Profile	25K sh + 2K SOAP
Notification Rate	OFF
UDR Response Timeout	5s
Client timeout	10s
Signaling Requests Latency Recorded on Client	NA
Provisioning Requests Latency Recorded on Client	NA

Note:

PNR scenarios are not tested because server stub is not used.

The following table describes cnDBTier resources and their utilization:

Table 3-17 cnDBTier Resources and their Utilization

Micro service name	Container name	Number of Pods	CPU Allocation Per Pod	Memory Allocation Per Pod	Total Resources	CPU Usage	Memory Usage
Management node	mysqlndbcluster	3	4 CPUs	10 GB	12 CPUs 30 GB Memory	0.2 CPU/pod	.2 GB/pod
Data node	mysqlndbcluster	4	15 CPUs	98 GB	64 CPU 408 GB Memory	5.8 CPU/pod	92 GB/pod
Data node	db-backup-executor-svc	4	100m CPU	128 MB	64 CPU 408 GB Memory	NA	NA
APP SQL node	mysqlndbcluster	4	16 CPUs	16 GB	64 CPUs 64 GB Memory	9.5 CPU/pod	8.8 GB/pod
SQL node (Used for Replication)	mysqlndbcluster	4	8 CPUs	16 GB	49 CPUs 81 GB Memory	Utilization data is not available for this service because of resource constraints, pods are not used.
DB Monitor Service	db-monitor-svc	1	200m CPUs	500 MB	3 CPUs 2 GB Memory	Minimal resources are used. Utilization is not captured
DB Backup Manager Service	replication-svc	1	200m CPU	500 MB	3 CPUs 2 GB Memory	Minimal resources are used. Utilization is not captured

cnDBTier Usage

Results for Kubectl top pods on cndbtier is shown below:

Results for Kubectl get hpa on cndbtier is shown below:

cnDBTier Metrics:

Data memory usage: 72GB (5.164GB used)
DB Reads per second: 52k
DB Writes per second: 24k

The following table describes UDR resources and their utilization:

Table 3-18 UDR Resources and their Utilization (Request Latency: 40ms)

Micro service name	Container name	Number of Pods	CPU Allocation Per Pod	Memory Allocation Per Pod	Total Resources	CPU Usage	Memory Usage
nudr-diameterproxy	nudr-diameterproxy	19	2.5 CPUs	4 GB	47.5 CPUs 76 GB Memory	1.75 CPU/pod	1 GB/pod
nudr-diam-gateway	nudr-diam-gateway	3	6 CPUs	4 GB	18 CPUs 12 GB Memory	.2.5 CPU/pod	2 GB/pod
Ingress-gateway-sig	ingressgateway-sig	2	2 CPUs	2 GB	4 CPUs 4 GB Memory	Minimal resources are used. Utilization is not captured
Ingress-gateway-prov	ingressgateway-prov	2	2 CPUs	2 GB	4 CPUs 4 GB Memory	1 CPU/pod	1 GB/pod
Nudr-dr-service	nudr-drservice	2	2 CPUs	2 GB	4 CPUs 4 GB Memory	Minimal resources are used. Utilization is not captured
Nudr-dr-provservice	nudr-dr-provservice	2	2 CPUs	2 GB	4 CPUs 4 GB Memory	1.4 CPU/pod	1 GB/pod
Nudr-nrf-client-nfmanagement	nrf-client-nfmanagement	2	1 CPUs	1 GB	2 CPUs 2 GB Memory	Minimal resources are used. Utilization is not captured
Nudr-egress-gateway	egressgateway	2	2 CPUs	2 GB	4 CPU 4 GB Memory	Minimal resources are used. Usage is not captured
Nudr-config	nudr-config	2	1 CPUs	1 GB	2 CPU 2 GB Memory	Minimal resources are used. Utilization is not captured
Nudr-config-server	nudr-config-server	2	1 CPUs	1 GB	2 CPU 2 GB Memory	Minimal resources are used. Utilization is not captured
alternate-route	alternate-route	2	1 CPUs	1 GB	2 CPU 2 GB Memory	Minimal resources are used. Usage is not captured
app-info	app-info	2	1 CPUs	1 GB	2 CPU 2 GB Memory	Minimal resources are used. Utilization is not captured
perf-info	perf-info	2	1 CPUs	1 GB	2 CPU 2 GB Memory	Minimal resources are used. Usage is not captured

Resource Utilization

Diameter resource utilization is shown below:
Diameter Usage

UDR HPA resource utilization is shown below:
UDR HPA

The following table describes provision gateway resources and their utilization:

Table 3-19 Provision Gateway Resources aand their Utilization (Provisioning Request Latency: 40ms)

Micro service name	Container name	Number of Pods	CPU Allocation Per Pod	Memory Allocation Per Pod	Total Resources	CPU Usage	Memory Usage
provgw-ingress-gatewa	ingressgateway	3	2 CPUs	2 GB	6 CPUs 6 GB Memory	1.3 CPU/pod	1 GB/pod
provgw-egress-gateway	egressgateway	2	2 CPUs	2 GB	4 CPUs 4 GB Memory	.0.9 CPU/pod	700 Mi/pod
provgw-service	provgw-service	4	2.5 CPUs	3 GB	10 CPUs 12 GB Memory	1.75 CPU/pod	1 GB/pod
provgw-config	provgw-config	2	1 CPUs	1 GB	2 CPUs 2 GB Memory	Minimal resources are used. Utilization is not captured
provgw-config-server	provgw-config-server	2	1 CPUs	1 GB	2 CPUs 2 GB Memory	Minimal resources are used. Utilization is not captured

Provisioning Gateway resource utilization is shown below:
ProvGW Usage

Resources calculation for UDR, Provisioning Gateway, and cnDbTier are shown below:

Table 3-20 cnUDR and ProvGw Resources Calculation

Resources	cnUDR			ProvGw
	Core services used for traffic runs (Nudr-diamgw, Nudr-diamproxy, Nudr-ingressgateway-prov and Nudr-dr-prov) at 70% usage	Other Microservices	Total	Core services used for traffic runs (ProvGw-ingressgateway, ProvGw-provgw service and ProvGw-egressgateway) at 70% usage	Other Microservice	Total
CPU	73.5	24	97.5	20	4	24
Memory in GB	96	24	120	22	4	26
Disk Volume (Ephemeral storage) in GB	26	16	42	9	4	13

Table 3-21 cnDbTier Resources Calculation

Resources	cnDbTier
	SQL nodes (at actual usage)	SQL Nodes (Overhead/ Buffer resources at 20%)	Data nodes (at actual usage)	Data nodes (Overhead/ Buffer resources at 10%)	MGM nodes and other resources (Default resources)	Total
CPU	76	16	23.2	5	18	138.5
Memory in GB	70.4	14	368	36	34	522
Disk Volume (Ephemeral storage) in GB	8	NA	960 (ndbdisksize= 240*4)	NA	20	988

Table 3-22 Total Resources Calculation

Resources	Total
CPU	260
Memory in GB	668 GB
Disk Volume (Ephemeral storage) in GB	104 GB

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-23 Result and Observation

Parameter	Values
Test Duration	18hr
TPS Achieved	10K
Success Rate	100%
Average UDR processing time (Request and Response)	40ms

3.4 Test Scenario 4: Policy Data Traffic Deployment Model

This section provides information about policy data traffic deployment model test scenarios.

3.4.1 Policy Data: 17.2K N36, 300 TPS Notifications and 500 TPS Provisioning

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

Signaling : 17.2K
Provisioning: 500 TPS
Total Subscribers: 10M

The following table describes the benchmarking parameters and their values:

Table 3-24 Traffic Model Details

Request Type	Details	TPS
N36 traffic (100%) 17.2K TPS for sm-data and subs-to-notify POST/DELETE	subs-to-notify POST	3K (17.45%)
	sm-data GET	4.7K (27.3%)
	subs-to-notify DELETE	3K (17.45%)
	sm-data PATCH	6.5K (37.8%)
500 TPS PROVISIONING Policy Data PUT Operation	UPDATE	300 (60%)
	GET	100 (40%)
	CREATE	50 (10%)
	DELETE	50 (10%)
NOTIFICATIONS (triggered from 300 PUT provisioning traffic)	POST Operation (Egress)	300

The following table describes the test case parameters and their values:

Table 3-25 Testcase Parameters

Input Parameter Details	Configuration Values
UDR Version Tag	24.2.0
Target TPS	17.2K Signaling
Notification Rate	300
UDR Response Timeout	2700ms
Signaling Requests Latency Recorded on Client	19ms
Provisioning Requests Latency Recorded on Client	24ms

Table 3-26 Consolidated Resource Requirement

Resource	CPU	Memory	Ephemeral Storage	PVC
cnDBTier	92 CPUs	485 GB	21 GB	1404 GB
UDR	215 CPUs	156 GB	48 GB	NA
Buffer	50 CPUs	50 GB	20 GB	200 GB
Total	357 CPUs	691 GB	89 GB	1604 GB

The following table describes cnDBTier resources and their utilization:

Table 3-27 cnDBTier Resources and their Utilization

Microservice name	Container name	Number of Pods	CPU Allocation Per Pod	Memory Allocation Per Pod	Ephemeral Storage Per Pod	PVC Allocation Per Pod	Total Resources	CPU Usage	Memory Usage	PVC Usage
Management node (ndbmgmd)	mysqlndbcluster	2	2 CPUs	9 GB	1 GB	15 GB	4 CPUs 18 GB Ephemeral Storage: 2 GB PVC Allocation: 30 GB	Minimal resources are used.		70 MB/pod
Data node (ndbmtd)	mysqlndbcluster	4	4 CPUs	93 GB	1 GB	132 GB Backup: 164 GB	16 CPUs 372 GB Ephemeral Storage: 4 GB PVC Allocation: 1184 GB	2 CPU/pod	77.5 GB/pod	33 GB/pod
APP SQL node (ndbappmysqld)	mysqlndbcluster	10	6 CPUs	4 GB	1 GB	2 GB	60 CPUs 40 GB Ephemeral Storage: 10 GB PVC Allocation: 20 GB	4.8 CPU/pod	2 GB/pod	200 MB/pod
SQL node (ndbmysqld,used for replication)	mysqlndbcluster	2	4 CPUs	24 GB	1 GB	13 GB	8 CPUs 48 GB Ephemeral Storage: 2 GB PVC Allocation: 26 GB	Minimal resources are used.		2 GB/pod
DB Monitor Service	db-monitor-svc	1	4 CPUs	4 GB	1 GB	NA	4 CPU 4 MB Ephemeral Storage: 1 GB	Minimal resources are used.		Minimal resources used
DB Backup Manager Service	backup-manager-svc	1	100 millicores CPUs	128 MB	1 GB	NA	1 CPU 128 MB Ephemeral Storage: 1 GB	Minimal resources are used.		Minimal resources used
Replication service (Multi site cases)	replication-svc	1	2 CPUs	2 GB	1 GB	143 GB	2 CPUs 2 GB Ephemeral Storage: 1 GB PVC Allocation: 143 GB	Minimal resources used		NA

The following table describes UDR resources and their utilization:

Table 3-28 UDR Resources and their Utilization (Average Latency: 19ms for N36 and 24ms for Provisioning)

Micro service name	Container name	Number of Pods	CPU Allocation Per Pod	Memory Allocation Per Pod	Ephemeral Storage Per Pod	Total Resources	CPU Usage	Memory Usage	CPU Utilization
Ingress-gateway-sig	ingressgateway-sig	9	6 CPUs	4 GB	1 GB	54 CPUs 36 GB Ephemeral Storage: 9 GB	2.4 CPU/pod	1.7 GB/pod	39%
Ingress-gateway-prov	ingressgateway-prov	2	4 CPUs	4 GB	1 GB	8 CPUs 8 GB Ephemeral Storage: 2 GB	0.5 CPUs/pod	1.1 GB/pod	11%
Nudr-dr-service	nudr-drservice	17	6 CPUs	4 GB	1 GB	102 CPUs 68 GB Ephemeral Storage: 17 GB	3 CPUs/pod	2 GB/pod	48%
Nudr-dr-provservice	nudr-dr-provservice	2	4 CPUs	4 GB	1 GB	8 CPUs 8 GB Ephemeral Storage: 2 GB	1.4 CPUs/pod	1.9 GB/pod	34%
Nudr-notify-service	nudr-notify-service	3	6 CPUs	5 GB	1 GB	18 CPUs 15 GB Ephemeral Storage: 3 GB	4.2 CPUs/pod	2.2 GB/pod	70%
Nudr-egress-gateway	egressgateway	2	6 CPUs	4 GB	1 GB	12 CPUs 8 GB Ephemeral Storage: 2 GB	0.75 CPUs/pod	1.2 GB/pod	10%
Nudr-config	nudr-config	2	1 CPU	1 GB	1 GB	2 CPUs 2 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Nudr-config-server	nudr-config-server	2	1 CPU	1 GB	1 GB	2 CPUs 2 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Alternate-route	alternate-route	2	1 CPU	1 GB	1 GB	2 CPUs 2 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Nudr-nrf-client-nfmanagement-service	nrf-client-nfmanagement	2	1 CPU	1 GB	1 GB	2 CPUs 2 GB Ephemeral Storage: 2 GB	Minimal resources are used.
App-info	app-info	2	1 CPU	1 GB	1 GB	2 CPUs 2 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Perf-info	perf-info	2	1 CPU	1 GB	1 GB	2 CPUs 2 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Nudr-dbcr-auditor-service	nudr-dbcr-auditor-service	1	1 CPU	1 GB	1 GB	1 CPU 1 GB Ephemeral Storage: 1 GB	Minimal resources are used.

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-29 Result and Observation

Parameter	Values
Test Duration	4h30m
TPS Achieved	17.2K Signaling
Success rate	100%

3.5 Test Scenario 5: 20K N36 and 1.3K Provisioning Profile (600 SOAP and 700 REST)

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

Signaling : 20K TPS
Provisioning: 1.3K
Total Subscribers: 35M

The following features are enabled for this testcase:

Auto Enrollment and Auto Create Features
Overload Handling
ETag (Entity Tag)
Ingress Gateway Pod Protection
Support for User-Agent Header
3gpp-Sbi-Correlation-Info Header
Suppress Notification

The following table describes the benchmarking parameters and their values:

Table 3-30 Traffic Model Details

Request Type	Details	TPS
N36 traffic 20K TPS	subs-to-notify POST	4K (20%)
	sm-data GET	4K (20%)
	subs-to-notify DELETE	4K (20%)
	sm-data PATCH	8K (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
REST PROVISIONING 700 TPS	DELETE (Cleaning the auto provisioned subscribers)	700

The following table describes the test case parameters and their values:

Table 3-31 Testcase Parameters

Input Parameter Details	Configuration Values
UDR Version Tag	24.3.0
Target TPS	20K TPS Signaling
Notification Rate	300
UDR Response Timeout	2.7s
Signaling Requests Latency Recorded on Client	25ms
Provisioning Requests Latency Recorded on Client	25ms

Table 3-32 Consolidated Resource Requirement

Resource	CPU	Memory	Ephemeral Storage	PVC
cnDBTier	97 CPUs	609 GB	21 GB	1815 GB
UDR	215 CPUs	155 GB	48 GB	NA
Buffer	50 CPUs	50 GB	20 GB	200 GB
Total	362 CPUs	814 GB	89 GB	2015 GB

The following table describes cnDBTier resources and their utilization:

Table 3-33 cnDBTier Resources and their Utilization

Microservice name	Container name	Number of Pods	CPU Allocation Per Pod	Memory Allocation Per Pod	Ephemeral Storage Per Pod	PVC Allocation Per Pod	Total Resources	CPU Usage	Memory Usage	PVC Usage
Management node (ndbmgmd)	mysqlndbcluster	2	2 CPUs	9 GB	1 GB	15 GB	4 CPUs 18 GB Ephemeral Storage: 2 GB PVC Allocation: 30 GB	Minimal resources are used.		6MB/pod
Data node (ndbmtd)	mysqlndbcluster	4	4 CPUs	124 GB	1 GB	132 GB Backup: 220 GB	16 CPUs 496 GB Ephemeral Storage: 4 GB PVC Allocation: 1408 GB	2 CPU/pod	117 GB/pod	6GB/pod
APP SQL node (ndbappmysqld)	mysqlndbcluster	10	6 CPUs	4 GB	1 GB	4 GB	60 CPUs 40 GB Ephemeral Storage: 14 GB PVC Allocation: 20 GB	3.9 CPU/pod	2.9 GB/pod	220MB/pod
SQL node (ndbmysqld,used for replication)	mysqlndbcluster	2	4 CPUs	24 GB	1 GB	110 GB	8 CPUs 48 GB Ephemeral Storage: 2 GB PVC Allocation: 220 GB	Minimal resources are used.		Minimal resources are used.
DB Monitor Service	db-monitor-svc	1	4 CPUs	4 GB	1 GB	NA	4 CPU 4 MB Ephemeral Storage: 1 GB	Minimal resources are used.		Minimal resources used
DB Backup Manager Service	backup-manager-svc	1	100 millicores CPUs	128 MB	1 GB	NA	1 CPU 128 MB Ephemeral Storage: 1 GB	Minimal resources are used.		Minimal resources used
Replication service (Multi site cases)	replication-svc	1	2 CPUs	2 GB	1 GB	143 GB	2 CPUs 2 GB Ephemeral Storage: 1 GB PVC Allocation: 143 GB	Minimal resources used		NA

The following table describes UDR resources and their utilization:

Table 3-34 UDR Resources and their Utilization (Average Latency: 25ms for N36 and Provisioning)

Micro service name	Container name	Number of Pods	CPU Allocation Per Pod	Memory Allocation Per Pod	Ephemeral Storage Per Pod	Total Resources	CPU Usage	Memory Usage	CPU Utilization
Ingress-gateway-sig	ingressgateway-sig	9	6 CPUs	4 GB	1 GB	54 CPUs 36 GB Ephemeral Storage: 9 GB	2.4 CPU/pod	3 GB/pod	39%
Ingress-gateway-prov	ingressgateway-prov	2	4 CPUs	4 GB	1 GB	8 CPUs 8 GB Ephemeral Storage: 2 GB	0.7 CPUs/pod	2.6 GB/pod	16%
Nudr-dr-service	nudr-drservice	17	6 CPUs	4 GB	1 GB	102 CPUs 68 GB Ephemeral Storage: 17 GB	2.4 CPUs/pod	2 GB/pod	38%
Nudr-dr-provservice	nudr-dr-provservice	2	4 CPUs	4 GB	1 GB	8 CPUs 8 GB Ephemeral Storage: 2 GB	1.8 CPUs/pod	2 GB/pod	45%
Nudr-notify-service	nudr-notify-service	3	6 CPUs	5 GB	1 GB	18 CPUs 15 GB Ephemeral Storage: 3 GB	Minimal resources are used.
Nudr-egress-gateway	egressgateway	2	6 CPUs	4 GB	1 GB	12 CPUs 8 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Nudr-config	nudr-config	2	1 CPU	1 GB	1 GB	2 CPUs 2 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Nudr-config-server	nudr-config-server	2	1 CPU	1 GB	1 GB	2 CPUs 2 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Alternate-route	alternate-route	2	1 CPU	1 GB	1 GB	2 CPUs 2 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Nudr-nrf-client-nfmanagement-service	nrf-client-nfmanagement	2	1 CPU	1 GB	1 GB	2 CPUs 2 GB Ephemeral Storage: 2 GB	Minimal resources are used.
App-info	app-info	2	1 CPU	1 GB	1 GB	2 CPUs 2 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Perf-info	perf-info	2	1 CPU	1 GB	1 GB	2 CPUs 2 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Nudr-dbcr-auditor-service	nudr-dbcr-auditor-service	1	1 CPU	1 GB	1 GB	1 CPU 1 GB Ephemeral Storage: 1 GB	Minimal resources are used.

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-35 Result and Observation

Parameter	Values
Test Duration	48h
TPS Achieved	20K Signaling
Success rate	100%

3.6 Test Scenario 6: 17.2K N36 + 10K SH and 1.2K Provisioning Profile (600 SOAP and 600 REST)

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

Signaling : 17.2K N36 + 10K SH
Provisioning: 1.2K
Total Subscribers: 35M

The following features are enabled for this testcase:

Auto Enrollment and Auto Create Features
Overload Handling
ETag (Entity Tag)
Ingress Gateway Pod Protection
Support for User-Agent Header
3gpp-Sbi-Correlation-Info Header
Suppress Notification
Subscriber Activity Logging
Diameter Gateway Pod Congestion Control

The following table describes the benchmarking parameters and their values:

Table 3-36 Traffic Model Details

Request Type	Details	TPS
N36 17.2K TPS	subs-to-notify POST	3.6K (20%)
	sm-data GET	3.6K (20%)
	subs-to-notify DELETE	3.6K (20%)
	sm-data PATCH	6.4K (40%)
SH 10K TPS	UDR	4K
	PUR	1.2K
	SNR	4.8K
SH PNR 700 TPS	PNR	700
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
REST PROVISIONING 600 TPS	DELETE (Cleaning auto provisioned subscribers)	600

The following table describes the test case parameters and their values:

Table 3-37 Testcase Parameters

Input Parameter Details	Configuration Values
UDR Version Tag	24.3.0
Target TPS	17.2K N36 + 10K SH
Notification Rate	700
UDR Response Timeout	2.7s
Signaling Requests Latency Recorded on Client	36ms
Provisioning Requests Latency Recorded on Client	36ms
Diameter (SH) Requests Latency Recorded on Client	40ms

Table 3-38 Consolidated Resource Requirement

Resource	CPU	Memory	Ephemeral Storage	PVC
cnDBTier	97 CPUs	609 GB	21 GB	1815 GB
UDR	215 CPUs	155 GB	48 GB	NA
Buffer	50 CPUs	50 GB	20 GB	200 GB
Total	362 CPUs	814 GB	89 GB	2015 GB

The following table describes cnDBTier resources and their utilization:

Table 3-39 cnDBTier Resources and their Utilization

Microservice name	Container name	Number of Pods	CPU Allocation Per Pod	Memory Allocation Per Pod	Ephemeral Storage Per Pod	PVC Allocation Per Pod	Total Resources	CPU Usage	Memory Usage	PVC Usage
Management node (ndbmgmd)	mysqlndbcluster	2	2 CPUs	9 GB	1 GB	15 GB	4 CPUs 18 GB Ephemeral Storage: 2 GB PVC Allocation: 30 GB	Minimal resources are used.		6MB/pod
Data node (ndbmtd)	mysqlndbcluster	4	4 CPUs	124 GB	1 GB	132 GB Backup: 220 GB	16 CPUs 496 GB Ephemeral Storage: 4 GB PVC Allocation: 1408 GB	2.1 CPU/pod	117 GB/pod	6GB/pod
APP SQL node (ndbappmysqld)	mysqlndbcluster	14	6 CPUs	4 GB	1 GB	4 GB	84 CPUs 56 GB Ephemeral Storage: 14 GB PVC Allocation: 20 GB	3.3 CPU/pod	2.5 GB/pod	220MB/pod
SQL node (ndbmysqld,used for replication)	mysqlndbcluster	2	4 CPUs	24 GB	1 GB	110 GB	8 CPUs 48 GB Ephemeral Storage: 2 GB PVC Allocation: 220 GB	Minimal resources are used.		Minimal resources are used.
DB Monitor Service	db-monitor-svc	1	4 CPUs	4 GB	1 GB	NA	4 CPU 4 MB Ephemeral Storage: 1 GB	Minimal resources are used.		Minimal resources used
DB Backup Manager Service	backup-manager-svc	1	100 millicores CPUs	128 MB	1 GB	NA	1 CPU 128 MB Ephemeral Storage: 1 GB	Minimal resources are used.		Minimal resources used
Replication service (Multi site cases)	replication-svc	1	2 CPUs	2 GB	1 GB	143 GB	2 CPUs 2 GB Ephemeral Storage: 1 GB PVC Allocation: 143 GB	Minimal resources used		NA

The following table describes UDR resources and their utilization:

Table 3-40 UDR Resources and their Utilization (Average Latency: 36ms for N36 and Provisioning. Diameter (SH) is 40ms.

Micro service name	Container name	Number of Pods	CPU Allocation Per Pod	Memory Allocation Per Pod	Ephemeral Storage Per Pod	Total Resources	CPU Usage	Memory Usage	CPU Utilization
Ingress-gateway-sig	ingressgateway-sig	9	6 CPUs	4 GB	1 GB	54 CPUs 36 GB Ephemeral Storage: 9 GB	2.2 CPU/pod	3 GB/pod	33%
Ingress-gateway-prov	ingressgateway-prov	2	4 CPUs	4 GB	1 GB	8 CPUs 8 GB Ephemeral Storage: 2 GB	0.7 CPUs/pod	2.6 GB/pod	16%
Nudr-dr-service	nudr-drservice	17	6 CPUs	4 GB	1 GB	102 CPUs 68 GB Ephemeral Storage: 17 GB	2.2 CPUs/pod	2 GB/pod	33%
Nudr-dr-provservice	nudr-dr-provservice	2	4 CPUs	4 GB	1 GB	8 CPUs 8 GB Ephemeral Storage: 2 GB	1.8 CPUs/pod	2 GB/pod	45%
Nudr-notify-service	nudr-notify-service	3	6 CPUs	5 GB	GB	18 CPUs 15 GB Ephemeral Storage: 3 GB	0.9 CPUs/pod	2.2 GB/pod	15%
Nudr-egress-gateway	egressgateway	2	6 CPUs	4 GB	1 GB	12 CPUs 8 GB Ephemeral Storage: 2 GB	0.6 CPUs/pod	1.2 GB/pod	8%
Nudr-diam-gateway	nudr-diam-gateway	2	6 CPUs	5 GB	1 GB	12 CPUs 10 GB Ephemeral Storage: 2 GB	2.5 CPUs/pod	2 GB/pod	40%
Nudr-diameterproxy	nudr-diameterproxy	9	6 CPUs	4 GB	1 GB	54 CPUs 36 GB Ephemeral Storage: 9 GB	2 CPUs/pod	2 GB/pod	33%
Nudr-config	nudr-config	2	1 CPU	1 GB	1 GB	2 CPUs 2 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Nudr-config-server	nudr-config-server	2	1 CPU	1 GB	1 GB	2 CPUs 2 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Alternate-route	alternate-route	2	1 CPU	1 GB	1 GB	2 CPUs 2 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Nudr-nrf-client-nfmanagement-service	nrf-client-nfmanagement	2	1 CPU	1 GB	1 GB	2 CPUs 2 GB Ephemeral Storage: 2 GB	Minimal resources are used.
App-info	app-info	2	1 CPU	1 GB	1 GB	2 CPUs 2 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Perf-info	perf-info	2	1 CPU	1 GB	1 GB	2 CPUs 2 GB Ephemeral Storage: 2 GB	Minimal resources are used.
Nudr-dbcr-auditor-service	nudr-dbcr-auditor-service	1	1 CPU	1 GB	1 GB	1 CPU 1 GB Ephemeral Storage: 1 GB	Minimal resources are used.

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-41 Result and Observation

Parameter	Values
Test Duration	72h
TPS Achieved	17.2K N36 + 10K SH
Success rate	100%