Archive: Posts

PernixData’s FVP vs. Virtunet – Both VMware Kernel Write Caching Software

More similar than different

Both us and PernixData differentiate from rest of the host side caching vendors in similar ways – that we are kernel mode software; both of us cache writes in addition to reads; have data protection strategies in place to prevent against data loss in case of multiple simultaneous hardware failure; do not require networking or storage to be reconfigured; and do not require agents per VM or VM per host.

Below is how we compare on the most important criteria one should be looking for in host side caching software.

Feature Virtunet’s VirtuCache PernixData’s FVP
Kernel mode software deployed on the hosts being accelerated with both a vCenter plugin and web GUI for management Yes Yes
Operating Systems supported ESXi 5.x, 6.x ESXi 5.x, 6.0 (not 6.5)
Caches hot data from any SAN based storage appliance Yes Yes
Caches reads and writes Yes Yes
In case of write cache, protects data loss if host or SSD fails by replicating writes to one or more SSDs in one or more hosts in the VMware cluster* Yes* Yes*
Continuously syncs write cache from in-host SSD or RAM to backend storage appliance Yes Yes
Signed and certified by VMware Yes Yes
Supports any in-host high speed media – SSD (SATA, SAS, PCIe, NVME) and/or RAM as caching media Yes Yes
Support for third party multi-pathing plugins** Yes** No**

* Differences between Pernix and Virtunet architecture with regards to data protection in case of host/cluster/datacenter failure

Both Pernix and Virtunet cache writes to in-host SSDs without synchronously committing the writes to backend storage appliance. This aspect accelerates writes but also introduces the possibility of data loss in case of host failure, since at any point in time there will be writes on the in-host SSD that are not synced with backend storage. With both PernixData FVP and Virtunet VirtuCache, the VMware cluster can remain operational and there will be no data loss in case a maximum of two hosts fail simultaneously. The reason is that in both software, all writes are simultaneously written to either one or two additional SSDs in one or two additional hosts in the VMware cluster. The number of copies of writes distributed across SSDs and across hosts is an admin configurable option called replication factor. Now if the replication factor was 2x, and if a maximum of two hosts were to crash at the same time, both us and Pernix will immediately sync the backend storage appliance from the mirrored copy of the write cache from a third host. In this respect the functionality between Pernix FVP and VirtuCache is similar. However in case the entire datacenter were to lose power or for some other reason all hosts were to fail at the same time, with PernixData, you will have data loss when the hosts are brought back up, whereas with Virtucache, there will be no data loss in this situation.

** Differences between Pernix and Virtunet in their support for third party multi-pathing plugins

The advantage of VirtuCache over PernixData is that in cases where customers insist on using non VMware multi-pathing plugins (MPP) from storage vendors like Nimble Storage, Dell Equallogic or EMC (Power Path), PernixData will not work. PernixData’s FVP needs to replace these MPPs with VMware Native Multi-path Plugin (NMP).

By default, VirtuCache is also a path selection plugin to VMware NMP, however if the customer insists on keeping their existing storage vendor MPP, Virtunet has an alternate software driver that does not require third party MPPs to be replaced.

As a side note, this article was inspired by an unusually large number of queries we are getting from users of PernixData FVP software who are looking for an alternative. This is most likely because PernixData’s FVP platform is being sunset as a result of their getting acquired for less than the money invested in them, in an all too familiar Silicon Valley story line of a heavily funded startup not being able to ramp revenues fast enough despite good tech. On the other hand we are entirely employee owned and profitable. How we run our business and our resulting longevity, which in turn results in long term relationship with our customers, might be a bigger differentiator than technical merit. That thread of VC funded businesses vs. customer funded ones is a topic for another blog post.;-)