09.03.2015 Views

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Diagnostics and <strong>Troubleshooting</strong> <strong>Reference</strong> <strong>Manual</strong> – Virtual SAN<br />

(VMDK) versus a large number of VMs with a small working set (VMDK).<br />

A VMDK size of 1GB for IOmeter should be more than sufficient. However<br />

you might be able to tune the IOmeter working set by choosing a specific<br />

number of sectors to work on, if I remember correctly.<br />

4. Be aware of creating a large working set; you can fill cache and then your<br />

performance will be based on magnetic disk performance due to cache<br />

misses.<br />

5. Be aware of using sustained sequential workloads – these will not benefit<br />

from cache. Use random workloads or a mix of workloads to make full use<br />

of Virtual SAN’s cache layer. Pure sequential workloads are rare, but<br />

important. Virtual SAN may not be best suited to these workload types.<br />

6. Use <strong>VSAN</strong> Observer to check read cache hit rate and write buffer<br />

evictions/destaging.<br />

7. How many vCPUs do your VMs running IOmeter have versus number of<br />

pCPUs? Scheduling these VMs could be a problem if there is contention,<br />

so check if these VMs are counting up “ready to run” (%READY)<br />

indicating that there is no pCPU resources for them to run on. However<br />

you will also need to balance this with a number of vCPUs that can drive<br />

adequate I/O. Don’t overdo it on number of VMs or number of vCPUs per<br />

VM.<br />

8. Do not set very large Outstanding I/O (OIO) when running lots of VMs<br />

and worker threads. OIO settings between 2 & 8 per VM should be<br />

sufficient.<br />

9. Read/Write mix – start with the traditional “transactional mix” is 70%<br />

read, 30% write. You can also try a 50/50 configuration, which is<br />

considered write intensive. You can later change to a different mix: e.g.<br />

35% read, 65% write and 65% read, 35% write.<br />

10. Set your I/O Size to at least 4KB. However, depending on workload, you<br />

might want something bigger.<br />

11. The observed average latency should be below 5ms, and the max latency<br />

should also be below 50ms. Your numbers may actually be substantially<br />

better, but the conservative numbers are given to cover a wider range of<br />

devices.<br />

V M W A R E S T O R A G E B U D O C U M E N T A T I O N / 2 5 8

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!