Category Archive for: ‘VirtuCache’

VMware View Storage Accelerator (VSA), a.k.a. Content Based Read Cache (CBRC), versus Virtunet VirtuCache

VSA caches only those blocks that are shared by all VDI VMs, and it can only use a maximum of 2GB host RAM. Because of these two reasons, it ends up caching only a small subset of blocks from the master VM 1. In comparison, VirtuCache caches all storage IO, both reads and writes, whether it is from master VM, end user VDI VMs, server VMs, ESXi kernel, and it can cache to large amounts of in-host SSD and/or RAM. These two aspects of VirtuCache ensure that almost all storage IO is serviced from...

How to Select SSDs for Host Side Caching for VMware – Interface, Model, Size, Source and Raid Level ?

In terms of price/performance, enterprise NVME SSDs have now become the best choice for in-VMware host caching media. They are higher performing and cost just a little more than their lower performing SATA counterparts. The Intel P4600/P4610 NVME SSDs are my favorites. The Samsung PM1725a is my second choice. If you don’t have a spare 2.5” NVME or PCIe slot in your ESXi host, which precludes you from using NVME SSDs, you could use enterprise SATA SSDs. If you choose to go with SATA SSDs,...

Improving Storage Performance of Dell VRTX

Dell's PowerEdge VRTX hyper-converged appliance can either have all hard drive datastores or all SSD datastores, but you can't have SSDs act as tiering or caching media for HDD volumes. That's where VirtuCache comes in.

GUI comparison, PernixData FVP vs Us – VMware Write Back Caching Software.

For the most part both our GUI and workflows are similar. This article compares, with screenshots, steps to install and configure VirtuCache and PernixData FVP. The only differences between us and Pernix stem from the fact that we leverage VMware's own capability in the areas of clustering, license management, and logging, whereas Pernix programmed these features separately within their software. Overall these additional screens add a few clicks and pages in Pernix versus us, but again I...

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. This article is the first in a series of two articles that...

Infinio’s Read Caching versus Virtunet’s Read+Write Caching Software

The biggest difference is that we accelerate both reads and writes, Infinio accelerates only reads. A few others are - with us you can apply caching policy at the datastore and/or VM level versus only at the VM level with Infinio; we accelerate creation of VMs, snapshots, and other VMware kernel operations, which they don't. More details in the table below. Virtunet Systems Infinio Accelerates both reads and writes.1 Accelerates only reads. By not caching writes, not only are writes...

VMware’s vFlash Read Cache (VFRC) versus Virtunet’s Read+Write Caching

BREAKING NEWS, April 20, 2019 : VMware will discontinue VFRC starting in ESXi 7.0. 0 Despite the end-of-life announcement for VFRC, if you still want to review the differences between VFRC and VirtuCache, below are the three most important ones. We cache reads and writes, VMware's VFRC caches only reads. Caching writes improves the performance of not only writes, but also of reads, and even in a read dominated workload.1 We require no ongoing administration. Caching in our case is fully...