Regular VM vs Pernix FVP write back vs FVP write trough

So since I’ve been working on FVP the last couple of days, I decided to go a simple test. First of I have one VM which is not accelerated by anyway, then I move it to a write trough mode (meaning that writes are not accelerated since Pernix needs to maintain writes to the datastore. Last I decided to setup a Write back (meaning that writes are stored on the cache and then back to the datastore.

So just a regular file benchmarking test….

image

Now using write back we can see that IOPS on writes are close to the same as it was before, but the reads are accelerated by the cache

image

This was the test using Write back, on creating a file on 2 GB I was closely to 6000 IOPS 4K.

image

The problem with write back is that writes are stored on the ram cache in this case, but Pernix has a feature called Fault tolerant write back, meaning that all writes are replicated to another host in the cluster.

And note you can use Add-PrnxVirtualMachineToFVPCluster -FVPCluster pernix -Name felles-sf -NumWBPeers 1 –WriteBack

to move a virtual machine to a writeback cluster.

#pernix-data