A Principled Technologies test report 11
Cisco UCS B230 M2 Blade Server:
Uncompromised virtual desktop performance
APPENDIX B - HOW WE TESTED
To determine the number of virtual desktops the server could support, we ran incremental tests increasing the
virtual desktop load until the processors on the Cisco UCS B230 M2 Blade Server were nearly saturated. We ensured that
the total response time for the seven office tasks never achieved a Login VSI Index average of 4,000 ms (VSI Max). We
confirmed there were no other factors such as storage bottlenecks or memory constraints that could contribute to a loss
of performance or response time.
Figure 5 illustrates our test environment: one Cisco UCS 5108 Blade Chassis with one Cisco UCS B230 M2 Blade
Server and one Cisco UCS B200 M2 blade server. The Cisco UCS B200 M2 blade server with VMware vSphere 5 hosted all
VMware View 5 and Login VSI Infrastructure VMs and the Cisco B230 M2 blade server with VMware vSphere 5 hosted all
the VMware View 5 virtual desktops. We connected the Cisco UCS 5108 Blade Chassis to redundant pair of Cisco UCS
6120XP Fabric Interconnects. We connected the Fabric Interconnects to a Cisco Nexus™ 5010 switch. We deployed the
two Cisco blade servers via the Cisco UCS Manager. Using Cisco Service Profiles, we assigned a Base firmware level of
2.0(1s) for all server components. We assigned each server two redundant 10Gb vNICs that had access to our data, and
NFS networks. We hosted all VM storage on a NFS export hosted on an EMC VNX 5500. We set up our VMware View
virtual desktops via a linked clone pool. Our master image, a Microsoft Windows 7 x 64 Enterprise VM, has one vCPU
and 2 GB of reserved memory. We chose 2 GB of memory because Microsoft requires that amount for x64 editions of
Windows 7. See http://windows.microsoft.com/en-US/windows7/products/system-requirements.
Note that, for its UCS blade servers, Cisco recommends a stateless boot from SAN configuration to ensure
portability. However, for simplicity we installed our vSphere operating system on local disks because it did not impact
the performance testing.
Figure 6 illustrates our logical network layout. We created a vSwitch on each vSphere server and created a single
port group, tagged as vlan100. We connected all virtual desktops, Login VSI launchers, and VMware view infrastructure
to these two vSwitches.
(82 pages)
(208 pages)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comments to this Manuals