# Add option to disable backup compression

**URL:** <https://meta.discourse.org/t/add-option-to-disable-backup-compression/37288>\
**Category:** Feature\
**Created:** [December 30, 2015, 10:43pm UTC](https://meta.discourse.org/t/add-option-to-disable-backup-compression/37288 "2015-12-30T22:43:36Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![DeanMarkTaylor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/deanmarktaylor/32/102462_2.png) [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)\
**Post date:** [January 13, 2016, 1:06am UTC](https://meta.discourse.org/t/add-option-to-disable-backup-compression/37288/14 "2016-01-13T01:06:18Z")

</div>

There is more likely to be some wiggle-room in resources / walk-clock time from piping the output from the currently separate commands.

Currently a 8GB+ tar file is written to disk, then read from disk gziped, then the 8GB gzipped file written to disk…  
… it seems to me a simple piping of the several outputs though would save resources and time.

(I haven’t tested this)

---

_[View the full topic](https://meta.discourse.org/t/add-option-to-disable-backup-compression/37288)._