How To Set Up A New Virtual Data Optimizer Device Using Cockpit Web Admin Console
In Red Hat Enterprise Linux 7.5, we’ve introduced virtual data optimizer (VDO). VDO allows you to save disk space and reduce replication bandwidth with the help of data compression and data deduplication.
In this blog post I want to walk you through how you can use the cockpit Web admin console that comes with Red Hat Enterprise Linux, to set up VDO and save substantial amount of space for your virtual machine images.
If you run a lot of VMs of the same OS, then you typically have a lot of bits that are the same, over and over again. A lot of the data that makes up the operating system is identical between the hosts. As your deployment grows with new VMs, the more storage you need to buy, even though a lot of the bits in the VMs are the same.
As you can see, I run a couple of Virtual Machines on this host.
If we go over to the storage page, we see that we’re using 100 GiB gigabytes to store these images. Running short on disk space.
So let’s try and see what happens if we move the VM images to a VDO device instead.
We create a new VDO device and select a empty block device.
We set both compression and deduplication. Most of the time this is the best choice, but both of these features have overhead. For example, compression consumes extra CPU resources. If data being stored is already compressed, as is the case with multimedia file formats (jpg, gif, mp3, mp4, etc..) , then the compression option should be disabled. Similarly textual database content (such as XML data) compresses well, but there aren’t likely to be duplicate 4K blocks in a single database instance. For the primary database application server, turning dedupe off and enabling compression can boost performance.
Read the entire article here, How To Set Up A New Virtual Data Optimizer Device Using Cockpit Web Admin Console – Red Hat Enterprise Linux Blog
Via the fine folks at Red Hat.