Just wanted to share with you my latest change within my lab.
I recently got a nice deal on some SSDs, and such changed a bit my Storage environment for my nested/test labs. As I really don’t care about protection/backup for my “test/dev” labs I do have a similar setup to this one.
Here are the main differences:
I’m not going to depict the install process as it is fairly easy and well explained in the documentations pages below:
As most Home Labs are not 10GB (cost is still pretty high) or more (I’m not geek enough to put Infiniband@home), and with the current performance level of SSDs or even HDDs, depending the operations, Network can be our limiting factor (1GB is around 125MB/s in theory). One of the probably most used operations in a lab, is cloning VMs in my case (deploying templates, copying VMs) and here is what it could look like on my old QNAP TS-809 Pro:
As you can notice, I’m facing contention with my network bandwidth here.
Here are some quick tests with QUADStor Appliance using VAAI through iSCSI (Using the same 1GB Network). Deploying template from internal storage to the QUADStor Storage Appliance I built.
From vSphere (Datastore):
Template: Windows 2008 R2 x64 Updated with some tools on it.
Size: 14500MB (14.5GB) Used on a 60GB VM.
I’ll give you a bit of background of what happened in the next screenshot. First I’ve deployed this template from my ESXi local Datastore to the QUADStor Appliance Datastore, and then I cloned it multiple times within that same Datastore to check the VAAI XCOPY primitive process and compare that relative performance to normal clones.
Some statistics on the QUADStor Web UI:
Here are some results:
Normal clone speed: 14500/((4×60)+35) ~= 52MB/s
VAAI clone speed: 14500/38 ~= 381MB/s (I took an average of the 4 clones processing time to get the idea)
As you can see I’m way over the Gigabit network speed (about 3 times more in those tests), and not consuming any of it, thanks to VAAI XCOPY.
PS: I also wanted to thank QUADStor support for helping me setup this with Debian & ZFS which was not tested and I did face an issue with block devices not being created on Linux, which was linked to this post (Basically until you specify a size for your vol/filesystem, Linux doesn’t currently create the devices in /dev, which is what QuadStor relies on for detecting ZFS)
You could also use linux software raid (mdadm) which is supported too, instead of ZFS.
Hope this might help some people labs/VMware VAAI testing, have fun :-)
- vStorage APIs for Array Integration FAQ (1021976)
- VMware vSphere® Storage APIs – Array Integration (VAAI)
EDITED: 26 June 2013 12:21 CET QUADStor is now Open Source ! Check here