White Papers

BP1024 Scaling and Best Practices for Virtual Workload Environments with the FS7500 36
Table 4 I/O mix for FS7500 scaling studies
Application # of
VMs
Per
block
Planned
IOPS per
VM
Actual IOPS per VM
Test 1 Test 2A (2
blocks)
Test 2B (2.33
blocks)
Test 3 (3
blocks)
Windows
Servers (for
running
Active
Directory,
Domain
Controllers
etc.)
1 30 *20 *20 *24 *20
Mail servers
like
Microsoft
Exchange
Server
1
500 for
Database
data, 200
for Log data
335 for
Database
data, 135 for
Log data
335 for
Database
data, 135 for
Log data
390 for
Database
data, 160 for
Log data
335 for
Database
data, 135 for
Log data
OLTP DB
servers like
Microsoft
SQL Server
4 1200 for
Database
data, 300
for Log data
800 for
Database
data, 200
for Log data
800 for
Database
data, 200 for
Log data
930 for
Database
data, 230 for
Log data
800 for
Database
data, 200
for Log data
Microsoft
SharePoint
Servers
1 1000 670 670 780 670
Web servers
like
Microsoft IIS
8 100 67 67 78 67
Middleware
servers like
J2EE App
servers
4 30 *20 *20 *24 *20
Web
2.0/Social
Media
applications
like Olio
1 100 67 67 78 67
Total IOPS
8350
5593
11186
13084
16716
+-5% variation when actually running the workload
*In the case of small workloads like Middleware servers, Iometer was unable to generate very few
IOPS with the basic minimal settings, so we combined workloads of two Middleware servers on one
VM and the other VM remained running without a workload
Test 2:
For the second test, two blocks of VMs were built across the two ESXi hosts. The final I/O mix from
test 1 in Table 4 was run scaled as two blocks of VMs. The configuration could easily handle this
workload and the response time was 10.88 ms. The achieved I/O mix for this test is listed in Table 4 in
the column labeled Test 2A.