![vmware esxi 6 mybook as datastore vmware esxi 6 mybook as datastore](https://img.sysnettechsolutions.com/How-to-Install-VMware-Tools-for-MacOS-High-Sierra-in-VMware-ESXi-MacOS-High-Sierra-VMware-Tools-Kurulumu-04.png)
The distributed shared storage system is a part of the hypervisor, where key aspects of the storage system are part of the kernel. Depending on the particular HCI solution, this virtual appliance on each host may also be responsible for a number of other duties. A VM lives on each host in the cluster, delivering a distributed shared storage plane, processing I/O and the other related activities. The two basic categories, as illustrated in Figure 1 are: All HCI solutions will vary (some more than others) on how they provide storage services to the VMs while maintaining resources for guest VM activity. HCI solutions available in today’s market not only offer different data services, but are built differently, which is just one of the many reasons why it is difficult to generalize a typical amount of overhead that is needed to process storage I/O. The latter is often never considered, yet extremely important. Efficiency of I/O delivery to and from VMs matter not only from performance and consistency as seen by the VM, but how much resource usage is introduced to the hosts in the cluster. Storage efficiency in HCI relates to the efficiency of how I/Os are delivered to and from the VM. With hyper-converged infrastructures, this term takes on additional meaning. The term "storage efficiency" is commonly associated with just data deduplication and compression. "Storage efficiency" is more than what you think
#Vmware esxi 6 mybook as datastore series#
Operational comparisons are not covered in this series simply to maintain focus on the intent of this series. This multi-part series is going to look at the basics of HCI architectures, and how they behave differently with respect to their demands on CPU, memory, and network resources. These responsibilities consume host resources. These responsibilities not only include handling VM storage I/O from end to end, but due to the distributed nature of HCI, hosts will take part in storage activity of VMs not local to the host, such as replicated writes of a VM, as well as data at rest operations and other services related to storage. With HCI, host resources (CPU, memory, and network) are now responsible for an entirely new set of duties typically provided by a storage array found in a traditional three-tier architecture. The architecture used by HCI solutions should not be overlooked, as these technical costs can not only influence the performance and consistency of the VMs, but dramatically impact the density of VMs per host, and ultimately the total cost of ownership. For an administrator, it can be a bit challenging to measure and understand. The amount attributed to this technical cost can vary quite drastically, and depends heavily on the architecture used. These technical costs could be thought of as a usage “tax” or “overhead” on host resources.
![vmware esxi 6 mybook as datastore vmware esxi 6 mybook as datastore](https://www.nakivo.com/blog/wp-content/uploads/2020/07/Opening-the-datastore-browser-by-using-VMware-Host-Client.png)
Yet, HCI also introduces new considerations in understanding and measuring technical costs associated with the architecture. Hyper-converged infrastructures (HCI) can bring several design and operational benefits to the table, adding to the long list of reasons behind its popularity.