It is here! PernixData FVP 2.0. During the last couple of months I have been getting experience with this in my lab and at selected customers. In 2.0 we are introducing 4 new groundbreaking capabilities.
Distributed Fault Tolerant Memory (DFTM):
Now we support the use of RAM for read and write acceleration. We still support the use of flash of course. We are just giving extra options for acceleration. From my experience in my lab RAM is INSANELY fast. It did not matter what kind of IO I threw at it. It just consistently performed with extremely low latency. Just imagine reading and writing data from RAM with 0,08 millisecond!
This one does not require a lot of explanation. Now we support NFS datastores. It is implemented in the same transparent fashion as block storage. So absolutely no changes is made to the VM or NFS datastore.
User defined fault domains
With the use of RAM we also see the need to define your fault domains. If you are using RAM for Write acceleration you would probably like to have a copy of the Writes on a second host placed in a another RACK/Blades chassis/Datacenter. With fault domains you can now define your physical boundaries and make sure exactly where the writes are replicated to. This of course also works with flash.
Adaptive Network Compression
When we send the Writes over the PernixData network (default is vMotion but any vmkernel will work, you decide) we have seen in 1Gb environments that it can be a problem. In FVP 2.0 we will take a look at the data to be sent, and if it makes sense we will compress before we send it over the wire. This brings down the latency of WB +1/+2 policy in a 1Gb environment.
You can read the full press release here: