Cisco Cisco UCS B200 M3 Blade Server Libro blanco
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
© 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 24 of 36
Figure 17 shows the test results of Cisco UCS B230 M2, Transaction per Minute (TPM) is measured using
Performance monitor and it is recorded after adding 4 databases on each virtual machine into the same physical
machine. In this scenario we added 4 databases to each virtual machine and there were 7 virtual machines created
on the same physical machine.
Figure 17. Transaction per Minute Scaling After Adding Each Virtual Machine
Scenario 2: SQL Server Consolidation and Scalability Testing Using Cisco UCS B250 M2 with 10
GB and 100 GB Databases
GB and 100 GB Databases
Figure 18 shows the resource Utilization of Cisco UCS B250 M2, especially CPU and Memory resources measured
using esxtop tool after adding each Virtual Machine one after another with 4 small databases running on each
virtual machine and concurrently running OLTP workload on each virtual machine. In this testing process we
observed 88 percent of memory utilization and 98 percent CPU Utilization on the Physical server. As shown in the
graph, after scaling upto 11 virtual machines, the physical server CPU resources saturate and still left with more
memory resources. The reason for CPU saturat
ion is due to more number of virtual CPU’s (vCPU) created on the
Cisco UCS B250 M2 server, which supports upto 12 physical processor cores and 12 logical cores with Hyper
threading enabled. Each virtual machine created with 4 vCPU and 32GB of memory, in total we created upto 11
virtual machines
, using 44 virtual CPU’s and 352 GB of memory from the Physical machine. Workload rendered
the system CPU bound and near saturation of memory.