# Enquiry on performance issue using Virtual Data Optimizer (VDO) to save storage space

**URL:** <https://discuss.elastic.co/t/enquiry-on-performance-issue-using-virtual-data-optimizer-vdo-to-save-storage-space/295550>\
**Category:** Elasticsearch\
**Created:** [January 27, 2022, 7:06am UTC](https://discuss.elastic.co/t/enquiry-on-performance-issue-using-virtual-data-optimizer-vdo-to-save-storage-space/295550 "2022-01-27T07:06:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon17386273](https://avatars.discourse-cdn.com/v4/letter/a/d2c977/32.png) [@anon17386273](https://discuss.elastic.co/u/anon17386273)\
**Post date:** [January 27, 2022, 7:06am UTC](https://discuss.elastic.co/t/enquiry-on-performance-issue-using-virtual-data-optimizer-vdo-to-save-storage-space/295550/1 "2022-01-27T07:06:02Z")

</div>

Hi

I came across this RedHat Virtual Data Optimizer (VDO) storage software that can be used as an additional storage layer on top of my physical volume to perform compression & deduplication. This can significantly save space.

I was wondering if there will be any lag issue (similar problem when using remote storage)? Or we can implement this under the COLD tier (with minimum / zero write)?

Has anyone tried this?

Any help is appreciated!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 24, 2022, 7:06am UTC](https://discuss.elastic.co/t/enquiry-on-performance-issue-using-virtual-data-optimizer-vdo-to-save-storage-space/295550/2 "2022-02-24T07:06:07Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.