09.03.2015 Views

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

16. <strong>Troubleshooting</strong> Virtual SAN<br />

performance<br />

As highlighted in the introduction, VMware recommends using the Virtual SAN<br />

Health Services to do initial triage of performance issues. The Virtual SAN Health<br />

Services carry out a range of health checks, and may detect issues that can directly<br />

impact performance. The Health Services directs administrators to an appropriate<br />

knowledge base article depending on the results of the health check. The knowledge<br />

base article will provide administrators with step-by-step instruction to solve the<br />

problem at hand.<br />

Please refer to the Virtual SAN Health Services Guide for further details on how to get<br />

the Health Services components, how to install them and how to use the feature for<br />

troubleshooting common Virtual SAN issues.<br />

Virtual SAN performance expectations<br />

Virtual SAN is a fully distributed, scale-out storage system, designed to support the<br />

aggregate needs of multiple VMs in a cluster. As such, performance profiles can be<br />

different than what is frequently seen with traditional monolithic storage arrays.<br />

Virtual SAN is designed to maximize the number of application IOPS in a cluster,<br />

while minimizing CPU and memory consumption. As such, it uses a very different<br />

design point from arrays that have dedicated CPU and memory.<br />

While testing a single application in a <strong>VSAN</strong> cluster may be reasonable, a full<br />

performance picture will not emerge until multiple applications across the cluster<br />

are tested.<br />

As there is wide variability in supported <strong>VSAN</strong> configurations (flash devices such as<br />

SSDs, IO controllers, magnetic disks for hybrid configurations, etc.) and application<br />

workloads (cluster size, working set, read/write mix, IO size) the best advice is to<br />

test a proposed production configuration with a workload that is as close to<br />

expected as possible.<br />

I/O flow<br />

In order to successfully troubleshooting performance issues, a certain level of<br />

understanding of Virtual SAN internals is required. The intention is not to take a<br />

deep-dive into the all of the internal workings of Virtual SAN, but instead give you<br />

an appreciation of some of the basic operations. Let’s start with I/O flow.<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 4 3

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

Saved successfully!

Ooh no, something went wrong!