From: Roman Mamedov <rm@romanrm.net>
To: Petr Bena <benapetr@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: New tool to recursive compress / decompress of files
Date: Sat, 21 Mar 2015 23:22:25 +0500 [thread overview]
Message-ID: <20150321232225.5f7e997e@natsu> (raw)
In-Reply-To: <CA+4EQ5cL53dS5k8fPNauT1fPGaYXjKBSzo7jTt1nz5p=w+c_SQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
On Sat, 21 Mar 2015 18:56:12 +0100
Petr Bena <benapetr@gmail.com> wrote:
> unlike NTFS, compressing files in btrfs is not so simple
There shouldn't be any need to micro-manage compression on Btrfs on a
per-folder or per-file basis. Just mount the whole volume as compress=[method]
(but not compress-force), there shouldn't be any downside, on the contrary,
with the current ratio of CPU core count and their performance to disk I/O
speed, you are likely to even see a speed-up. Also files which are detected to
be incompressible are automatically skipped from compression (at least that's
what it tries to do by design).
If you want higher performance and less fragmentation on certain files/folders,
you are supposed to set them NOCOW, at which point the compression is also
automatically disabled.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-03-21 18:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 17:56 New tool to recursive compress / decompress of files Petr Bena
2015-03-21 18:08 ` Hugo Mills
2015-03-21 18:12 ` Petr Bena
2015-03-21 18:16 ` Petr Bena
2015-03-25 1:49 ` David Sterba
2015-03-25 1:42 ` David Sterba
2015-03-21 18:22 ` Roman Mamedov [this message]
2015-03-21 18:25 ` Petr Bena
2015-03-21 18:26 ` Petr Bena
2015-03-21 19:27 ` Marc MERLIN
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=20150321232225.5f7e997e@natsu \
--to=rm@romanrm.net \
--cc=benapetr@gmail.com \
--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.