Datrium DVX is deployed as a vSphere Installation Bundle (VIB) on top of each hypervisor host that is part of the Datrium DVX compute layer. Datrium calls this the "DVX Hyperdriver" software. The DVX Hyperdriver provides optimized access to data through local access to flash and a tight coupling with the Datrium DVX Data Nodes.
The Datrium DVX Hyperdriver requires a minimum of 8 CPU cores on a Compute Node, and can use a maximum of 10 CPU cores. When running DVX in "Fast" performance mode, the Hyperdriver uses a maximum of 20% (=2 CPU cores). When running in "Insane" performance mode, the Hyperdriver uses a maximum of 40% (=4 CPU cores) for dramatic increases in IOPs and throughput.
The Datrium DVX Hyperdriver uses 7.5 - 45.5 GiB of memory on the Compute Node, depending on the amount of Flash on the Compute Node that is dedicated for DVX use. The amount of memory used increases approximately 2.5 GiB for each additional TB of raw flash storage that is dedicated for DVX use.
Kernel Integrated, Virtual Controller and VIB are each distributed architectures, having one active component per virtualization host that work together as a group. All three architectures are capable of delivering a complete set of storage services and good performance. Kernel Integrated solutions reside within the protected lower layer, VIBs reside just above the protected kernel layer, and Virtual Controller solutions reside in the upper user layer. This makes Virtual Controller solutions somewhat more prone to external actions (eg. most VSCs do not like snapshots). On the other hand Kernel Integrated solutions are less flexible because a new version requires the upgrade of the entire hypervisor platform. VIBs have the middle-ground, as they provide more flexibility than kernel integrated solutions and remain relatively shielded from the user level.
Datrium, DVX [HCI]/188.8.131.52, x86
Hypervisor Deployment, Virtualization, Workload Support