From: Paul Hartman <paul.hartman+gentoo@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:39:37 -0500 [thread overview]
Message-ID: <CAEH5T2PNNDtZuC7Ci0wTg2cdcJXiNVuiqNQ9Jg5a2FNWyrMC+w@mail.gmail.com> (raw)
In-Reply-To: <CAA2qdGXB-v2T3euBsmmn44BMOUVg8BWFxh4ocfQ5mijhDfLOcg@mail.gmail.com>
On Tue, Aug 14, 2012 at 12:05 PM, Pandu Poluan <pandu@poluan.info> wrote:
>
> On Aug 14, 2012 11:42 PM, "Helmut Jarausch" <jarausch@igpm.rwth-aachen.de>
> wrote:
>>
>> On 08/14/2012 04:07:39 AM, Adam Carter wrote:
>>>
>>> > I think btrfs probably is meant to provide a lot of the modern
>>> > features like reiser4 or xfs
>>>
>>> Unfortunately btrfs is still generally slower than ext4 for example.
>>> Checkout http://openbenchmarking.org/, eg
>>> http://openbenchmarking.org/s/ext4%20btrfs
>>>
>>> The OS will use any spare RAM for disk caching, so if there's not much
>>> else running on that box, most of your content will be served from
>>> RAM. It may be that whatever fs you choose wont make that much of a
>>> difference anyways.
>>>
>>
>> If one can run a recent kernel (3.5.x) btrfs seems quite stable (It's used
>> by some distribution and Oracle for real work)
>> Most benchmark don't use compression since other FS can't use it. But
>> that's unfair. With compression, one needs to read
>> much less data (my /usr partition has less than 50% of an ext4 partition,
>> savings with the root partition are even higher).
>>
>> I'm using the mount options
>> compress=lzo,noacl,noatime,autodefrag,space_cache which require a recent
>> kernel.
>>
>> I'd give it a try.
>>
>> Helmut.
>>
>
> Are the support tools for btrfs (fsck, defrag, etc.) already complete?
Do they exist? Yes (sys-fs/btrfs-progs). Are they complete? Probably not...
next prev parent reply other threads:[~2012-08-14 19:42 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
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 [this message]
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=CAEH5T2PNNDtZuC7Ci0wTg2cdcJXiNVuiqNQ9Jg5a2FNWyrMC+w@mail.gmail.com \
--to=paul.hartman+gentoo@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