public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nilesh Govindrajan <contact@nileshgr.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fast file system for cache directory with lot's of files
Date: Mon, 13 Aug 2012 20:50:54 +0530	[thread overview]
Message-ID: <50291B56.9000506@nileshgr.com> (raw)
In-Reply-To: <CADPZhur83KuA8S5vvaQF8rDq-4ST-rAZubmJShdiE5PSc7_uag@mail.gmail.com>

On Mon 13 Aug 2012 08:28:15 PM IST, Michael Hampicke wrote:
>>     I guess traversing through directories may be faster with XFS,
>>     but in my experience ext4 perfoms better than XFS in regard to
>>     operations (cp, rm) on small files.
>>     I read that there are some tuning options for XFS and small
>>     files, but never tried it.
>>
>>     But if somone seconds XFS I will try it too.
>
>     It's been a while since I messed with this but isn't XFS the one
>     that hates power failures and such?
>
>     Dale
>
>     :-) :-)
>
>     --
>     I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
>
> Well, it's the delayed allocation of XFS (which prevents
> fragmentation) that does not like sudden power losses :) But ext4 has
> that too, you can disable it though - that should be true for XFS too.
> But the power situation in the datacenter has never been a problem so
> far, and even if the cache partition get's screwed, we can always
> rebuild it. Takes a few hours, but it would not be the end of the world :)

Yes, XFS hates power failures. I got a giant UPS for my home desktop to 
use XFS because of it's excellent performance ;-)

--
Nilesh Govindrajan
http://nileshgr.com


  reply	other threads:[~2012-08-13 15:23 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 [this message]
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
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=50291B56.9000506@nileshgr.com \
    --to=contact@nileshgr.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