From: Alecks Gates <alecks.g@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fast file system for cache directory with lot's of files
Date: Tue, 14 Aug 2012 14:55:51 -0500 [thread overview]
Message-ID: <CAKkyAYb5D856vvrj6CjTXpj3fzGOKXLCR6ap3NSjcCo=YprKmg@mail.gmail.com> (raw)
In-Reply-To: <502A8FD9.5030505@hadt.biz>
On Tue, Aug 14, 2012 at 12:50 PM, Michael Hampicke <gentoo-user@hadt.biz> wrote:
> Am 14.08.2012 19:42, schrieb Volker Armin Hemmann:
>> Am Dienstag, 14. August 2012, 13:21:35 schrieb Jason Weisberger:
>>> Sure, but wouldn't compression make write operations slower? And isn't he
>>> looking for performance?
>>
>> not really. As long as the CPU can compress faster than the disk can write
>> stuff.
>>
>> More interessting: is btrfs trying to be smart - only compressing compressible
>> stuff?
>>
>
> It does do that, but letting btrfs check if the files are already
> compressed, if you know, that they are compressed, is a waste of cpu
> cycles :)
>
Also look into the difference between compress and compress-force[0].
I wonder how much overhead checking whether or not to compress a file
costs. I use mount options similar to Helmut and get great results:
defaults,autodefrag,space_cache,compress=lzo,subvol=@,relatime
But most of my data is compressible. Compression makes such a huge
difference, it surprises me. Apparently on this Ubuntu system it
automatically makes use of all files on / as a subvolume in "@".
Interesting.
Anyway, btrfs-progs does include basic fsck now but I wouldn't use it
for anything serious[1].
[0] https://btrfs.wiki.kernel.org/index.php/Mount_options
[1] https://btrfs.wiki.kernel.org/index.php/Btrfsck
next prev parent reply other threads:[~2012-08-14 19:58 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 13:16 [gentoo-user] Fast file system for cache directory with lot's of files Michael Hampicke
2012-08-13 13:22 ` Nilesh Govindrajan
2012-08-13 13:54 ` Michael Hampicke
2012-08-13 14:19 ` Pandu Poluan
2012-08-13 14:42 ` Michael Hampicke
2012-08-13 14:52 ` Michael Mol
2012-08-13 15:26 ` Michael Hampicke
2012-08-13 15:52 ` Michael Mol
2012-08-13 17:14 ` Florian Philipp
2012-08-13 18:18 ` Michael Hampicke
2012-08-14 14:00 ` Florian Philipp
2012-08-14 17:42 ` Michael Hampicke
2012-08-13 14:40 ` Dale
2012-08-13 14:58 ` Michael Hampicke
2012-08-13 15:20 ` Nilesh Govindrajan
2012-08-13 14:38 ` Daniel Troeder
2012-08-13 14:53 ` Michael Hampicke
2012-08-14 8:21 ` Daniel Troeder
2012-08-14 9:46 ` Neil Bothwick
2012-08-14 13:00 ` Florian Philipp
2012-08-14 13:54 ` Daniel Troeder
2012-08-14 15:09 ` Florian Philipp
2012-08-14 15:33 ` Florian Philipp
2012-08-16 16:54 ` Neil Bothwick
2012-08-14 17:45 ` Michael Hampicke
2012-08-13 20:13 ` Paul Hartman
2012-08-13 20:41 ` Volker Armin Hemmann
2012-08-14 2:07 ` Adam Carter
2012-08-14 16:36 ` Helmut Jarausch
2012-08-14 17:05 ` Pandu Poluan
2012-08-14 17:21 ` Jason Weisberger
2012-08-14 17:42 ` Volker Armin Hemmann
2012-08-14 17:50 ` Michael Hampicke
2012-08-14 19:55 ` Alecks Gates [this message]
2012-08-14 20:17 ` Michael Mol
2012-08-14 20:57 ` Alecks Gates
2012-08-14 17:48 ` Michael Hampicke
2012-08-14 17:42 ` Volker Armin Hemmann
2012-08-14 19:39 ` Paul Hartman
2012-08-15 7:31 ` Bill Kenworthy
2012-08-15 8:13 ` Bill Kenworthy
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='CAKkyAYb5D856vvrj6CjTXpj3fzGOKXLCR6ap3NSjcCo=YprKmg@mail.gmail.com' \
--to=alecks.g@gmail.com \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox