In this section...
Overview
The Unable to show "metadata-from": No such page "_space_variables" performance metrics for simultaneous sessions for various call scenarios are summarized in the "Benchmarking Results" section of the following pages. Note that these numbers apply to our recommended CPU and memory configurations, and the results may vary depending on the actual CPUs used. Exceeding these simultaneous sessions metrics may result in poor call performance, including longer call setup times and/or poor voice quality. Unable to show "metadata-from": No such page "_space_variables" recommends maintaining call rates within the performance limits benchmarked below.
Server and VM Details
Server and VM Details
Configuration | Server Detail | VM Details | Max Link | |||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Server Type | CPU Speed (GHz) | Processor sockets | RAM (GB) | Hyperthreading | vCPUs allocated | Memory (GB) | Disk Size (GB) | Network Interface Mode | ||
| Config-1 | HP DL380 Gen10 Gold 6140 | 2.3 | 2 | 256 | ACTIVE | 4 | 32 | 100 | Pass-Through Mode (Direct I/O) | 10 Gbps |
| Config-2 | 8 | Pass-Through Mode (Direct I/O) | ||||||||
| Config-3 | 20 | SR-IOV | ||||||||
| Config-4 | 32 | SR-IOV | ||||||||
Note
For deployments that require it, you can instantiate the SBC SWe in smaller-sized configurations that use limited memory and vCPU resources. However, the limited resources place some restrictions on capacity and capabilities. Refer to Small SBC SWe Deployment Characteristics and Performance Metrics for Small SBC SWe Configurations for more information.
Benchmarking Setup
The two test beds used to collect benchmarking data are depicted below.
The VM is hosted on a single NUMA node, where the NIC is connected.
Benchmarking Setup for SBC SWe Using SR-IOV interfaces
Benchmarking Setup for SBC SWe Configured in Pass-Through Mode (Direct I/O)
Performance Metrics
This section includes benchmarking results using the following configurations with and without DoS. Contact your Unable to show "metadata-from": No such page "_space_variables" representative if you are interested in benchmarking data for other call scenarios.
VMware Benchmarking Results G729a passthru Call Mix (x-code G729a->G711u + G729a passthru)
Call Scenario/Configuration Config Traffic Profile CPS/CHT Simultaneous
Sessions G729a passthru Config-1 (4 vCPU) standard_passthrough_profile 40/46 1840 config-2 (8 vCPU) standard_passthrough_profile 200/78 15600 config-2 (8 vCPU) standard_callmix_profile 220/39 8580
KVM Hypervisor Benchmarking Results
Call Scenario/Configuration | Config | Traffic Profile | CPS/CHT | Simultaneous |
|---|---|---|---|---|
G729a passthru | Config-3 (20 vCPU) | standard_passthrough_profile | 600/77.5 | 46,500 |
x-code G729a->G711u | config-4 (32 vCPU) | standard_transcoding_profile | 180/31 | 5,580 |
G729a pass through with TLS/SRTP enabled on ingress leg | config-4 (32 vCPU) | standard_passthrough_profile | 500/88 | 44,000 |
G729a Direct Media | config-4 (32 vCPU) | standard_signaling_profile | 1000/40 | 40,000 |
Increasing RAM on Active SBC SWe Systems
Use the following procedure to increase RAM size on active (live) systems to increase SBC SWe session capacity.
| Step | Action |
|---|---|
| 1 | Power down the designated standby SBC. |
| 2 | Increase the RAM size of the VM system, and then power-on the standby SBC. |
| 3 | Perform a manual switchover, and then power-down the previously active SBC. Refer to the following pages for details: EMA: System - Admin CLI: Admin - CLI |
| 4 | Increase the RAM size of the VM system for the powered-down SBC, and then power it back up. |
| 5 | Manually switchover to revert the active/standby SBCs back to their original states prior to beginning this procedure. |
| 6 | Follow LSWU steps if you are upgrading to the next release. |
Overview
Content Tools