From: Marc Joliet <marcec@gmx.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: compression disk space saving - what are your results?
Date: Sat, 05 Dec 2015 14:37:05 +0100 [thread overview]
Message-ID: <6329794.eixGOkx0p3@thetick> (raw)
In-Reply-To: <4082684905f25f921ae4564b1c8a892e@admin.virtall.com>
[-- Attachment #1: Type: text/plain, Size: 2212 bytes --]
On Wednesday 02 December 2015 18:46:30 Tomasz Chmielewski wrote:
>What are your disk space savings when using btrfs with compression?
>
>I have a 200 GB btrfs filesystem which uses compress=zlib, only stores
>text files (logs), mostly multi-gigabyte files.
>
>
>It's a "single" filesystem, so "df" output matches "btrfs fi df":
>
># df -h
>Filesystem Size Used Avail Use% Mounted on
>(...)
>/dev/xvdb 200G 124G 76G 62% /var/log/remote
>
>
># du -sh /var/log/remote/
>153G /var/log/remote/
>
>
> From these numbers (124 GB used where data size is 153 GB), it appears
>that we save around 20% with zlib compression enabled.
>Is 20% reasonable saving for zlib? Typically text compresses much better
>with that algorithm, although I understand that we have several
>limitations when applying that on a filesystem level.
>
>
>Tomasz Chmielewski
>http://wpkg.org
I have a total of three file systems that use compression, on a desktop and a
laptop. / on both uses compress=lzo, and my backup drive uses compress=zlib
(my RAID1 FS does not use compression). My desktop looks like this:
% df -h
Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
/dev/sda1 108G 79G 26G 76% /
[...]
For / I get a total of about 8G or at least 9% space saving:
# du -hsc /mnt/rootfs/*
71G /mnt/rootfs/home
14G /mnt/rootfs/rootfs
2,3G /mnt/rootfs/var
87G insgesamt
I write "at least" because this does not include snapshots. On my laptop the
difference is merely 1 GB (83 vs. 84 GB), but it was using the autodefrag
mount option until yesterday (when I migrated it to an SSD using dd), which
probably accounts for a significant amount of wasted space. I'll see how it
develops over the next two weeks, but I expect the ratio to become similar to
my desktop (probably less, since there is also a lot of music on there).
I would love to answer the question for my backup drive, but du took too long
(> 1 h) so I stopped it :-( . I might try it again later, but no promises!
Greetings
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-12-05 13:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 9:46 compression disk space saving - what are your results? Tomasz Chmielewski
2015-12-02 10:36 ` Duncan
2015-12-02 14:03 ` Imran Geriskovan
2015-12-02 14:39 ` Austin S Hemmelgarn
2015-12-03 6:29 ` Duncan
2015-12-03 12:09 ` Imran Geriskovan
2015-12-04 12:33 ` Austin S Hemmelgarn
2015-12-04 12:37 ` Austin S Hemmelgarn
2015-12-02 13:03 ` Austin S Hemmelgarn
2015-12-02 13:53 ` Tomasz Chmielewski
2015-12-02 14:03 ` Wang Shilong
2015-12-02 14:06 ` Tomasz Chmielewski
2015-12-02 14:49 ` Austin S Hemmelgarn
2015-12-22 3:55 ` Kai Krakow
2015-12-22 17:25 ` james northrup
2015-12-05 13:37 ` Marc Joliet [this message]
2015-12-05 14:11 ` Marc Joliet
2015-12-06 4:21 ` Duncan
2015-12-06 11:26 ` Marc Joliet
2015-12-05 19:38 ` guido_kuenne
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6329794.eixGOkx0p3@thetick \
--to=marcec@gmx.de \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.