Re: definiing deduplication (was: Re: deduplicating file systems: VDO with Debian?)
On Tue, 2022-11-08 at 10:04 +0100, didier gaumet wrote:
> Le 08/11/2022 à 05:13, hw a écrit :
> > On Mon, 2022-11-07 at 13:57 -0500, rhkramer@gmail.com wrote:
> > >
> > >
> > > I didn't (and don't) know much about deduplication (beyond what you might
> > > deduce from the name), so I google and found this article which was
> > > helpful to
> > > me:
> > >
> > > *
> > > [[https://www.linkedin.com/pulse/lets-know-vdo-virtual-data-optimizer-
> > > ganesh-gaikwad][Lets know about VDO (virtual data optimizer)]]
> >
> > That's a good pointer, but I still wonder how VDO actually works.
> [...]
> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/vdo-integration
> and blog, that exposes performance trade-off:
> https://www.redhat.com/en/blog/look-vdo-new-linux-compression-layer
>
> from what I understand, VDO was designed as a layer in kernel space to
> provide deduplication and compression features to local or distributed
> filesystems that lack it. The goal being primarily to optimize storage
> space for a provider of networked virtual machines to entities or customers
>
Yes, I've seen those. I can only wonder how much performance impact VDO would
have for backups. And I wonder why it doesn't require as much memory as ZFS
seems to need for deduplication.
Reply to: