Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Test Result Summary of Standalone Running on KVM Hypervisor

 

The standalone SBR Carrier server is qualified to support Kernel-based Virtual Machine (KVM) hypervisor on a Red Hat Enterprise Linux 7.3 machine. The results shown in this section are tested with guest RHEL 7.3 VMs hosted on a RHEL 7.3 KVM hypervisor with the following hardware configurations:

  • The host has 128 GB RAM, 32 CPUs with 8 cores per CPU, and 1.5 TB storage capacity. SBR Carrier 8.4 is running on the clients.

Note

Overprovisioning of VMs is not recommended.

Note

The results shown in this section are obtained in an environment where very few applications or services are left running during the tests.

KVM Hypervisor Running with One VM and Varying CPU Counts

KVM Hypervisor Running with One VM and Varying CPU Counts

Table 46 describes the results of tests run on the KVM hypervisor running with one VM for local accounting–start only (no SQL, proxy, or directed accounting methods). The following results are tested with a thread configuration of 500.

On a VM, if the CPU count is increased, the session rate and CPU utilization are also increased as shown in Table 46. With the local accounting-start only load, the RADIUS process size increases with an increase in number of sessions in the in-memory session database.

Table 46: KVM Hypervisor Running with One VM

VM Configuration

Sessions/Second

CPU Utilization

RADIUS Process Size

2 CPUs with 2 Cores, 10 GB RAM

2450

304%

6 GB

4 CPUs with 4 Cores, 20 GB RAM

3695

283%

8.6 GB

8 CPUs with 4 Cores, 20 GB RAM

5072

459%

10.09 GB

16 CPUs with 4 Cores, 20 GB RAM

9555

573%

15.4 GB

Figure 11: KVM Hypervisor Running with One VM—Sessions per Second Versus CPU Utilization
KVM Hypervisor Running with One VM—Sessions per
Second Versus CPU Utilization

KVM Hypervisor Running with Six VMs

KVM Hypervisor Running with Six VMs

Table 47 describes the results of tests run on the KVM hypervisor running with six VMs for local accounting only. Each VM is configured with 16 GB RAM and 4 CPUs with 4 Cores per CPU.

Note

The six VMs do not communicate with each other. They are included as a baseline for having six standalone SBRs in the same hypervisor.

Table 47: KVM Hypervisor Running with Six VMs (4 CPUs x 4 Cores)

VM

Sessions/Second

CPU Utilization

VM1

9878

274%

VM2

5346

286%

VM3

5883

276%

VM4

5574

277%

VM5

4918

238%

VM6

4493

272%

Table 48 describes the results of tests run on the KVM hypervisor running with six VMs for local accounting only. Each VM is configured with 16 GB RAM and 4 CPUs with 8 cores.

Table 48: KVM Hypervisor Running with Six VMs (4 CPUs x 8 Cores)

VM

Sessions/Sec

CPU Utilization

VM1

7017

282%

VM2

5776

286%

VM3

7019

275%

VM4

7492

269%

VM5

6061

274%

VM6

5514

272%

Figure 12 compares the results of VMs configured with 4 CPUs x 4 cores and 4 CPUs x 8 cores. Doubling the number of cores per CPU increases the throughput without greatly increasing the CPU utilization.

Figure 12: KVM Hypervisor Running with Six VMs: 4 CPUs x 4 Cores Versus 4 CPUs x 8 Cores
KVM
Hypervisor Running with Six VMs: 4 CPUs x 4 Cores Versus 4 CPUs x
8 Cores

Accounting Start Only for Proxy

Accounting Start Only for Proxy

Table 49 describes the results of tests run in an environment where the proxy SBR Carrier is running on a VM and the target SBR Carrier is running on a separate physical machine. The following results are tested with an accounting thread configuration of 200, RecordLocally=1, and Block=1 (with Block=1, the accounting thread processes the proxy transaction; a separate thread is used for the transaction when Block=0).

Table 49: Accounting Start Only: Proxy SBR Carrier on a VM and the Target SBR Carrier on a Separate Physical Machine

Configuration

TPS7

CPU Utilization

HST File Size8

Proxy: 20 CPUs with 8 Cores, 100 GB RAM

5956

300%

921 MB

Target: 32 CPUs with 8 Cores, 250 GB RAM

6091

382%

913 MB

7TPS = (Total accounting requests - Dropped accounting packets) / 600 seconds

8Sessions are stored in the .hst file.

Table 50 describes the results of tests run in an environment where both the proxy and target are hosted as VMs on the same physical machine. The following results are tested with an accounting thread configuration of 200, test duration of 16 minutes, and Block=1.

Table 50: Accounting Start Only: Proxy and Target Hosted as VMs on the Same Physical Machine

Configuration

TPS

CPU Utilization

HST File Size

Proxy: 10 CPUs with 8 Cores, 50 GB RAM

6034

276%

926 MB

Target: 10 CPUs with 8 Cores, 50 GB RAM

6152

177%

916 MB

Comparing results of proxy and target that are hosted as VMs on the same physical machine (Table 50) and proxy on a VM and target on a separate physical machine (Table 49) provides approximately the same performance.