public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: markgw@sgi.com
Cc: xfs@oss.sgi.com
Subject: Re: is xfs good if I have millions of files and thousands of hardlinks?
Date: Tue, 19 Feb 2008 23:43:25 +0100	[thread overview]
Message-ID: <47BB5B8D.2060500@wpkg.org> (raw)
In-Reply-To: <47BB5873.6040703@sgi.com>

Mark Goodwin schrieb:

> defragmenting by copying from the ext3 filesystem to a new filesystem
> should help, for a while at least. Whether xfs would have an on-going
> performance problem compared to ext3 depends on your usage patterns ..
> does "all the time" mean you are continuously adding new files and links
> and removing files at a high rate/second? Are multiple threads doing this?

Yes. Multiple threads adding new files (or hardlinks, if there are such 
files already) all the time (24h/day).
Normally, there is only one thread removing the files. Because of this 
performance problem I described, it also does its job 24h/day - it just 
can't finish removing the unneeded files in a couple of hours, not to 
say one day.


> Are all the files the same size? Block-size been tuned?

No, file sizes are mostly random stuff you will normally find on any 
rootfs, home, etc. directory.
It's a backup system which uses hardlinks so that files which are 
already in backup do not take additional place.

I didn't do any block-size tuning, as I don't really know where to bite.


-- 
Tomasz Chmielewski
http://wpkg.org

  reply	other threads:[~2008-02-19 22:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19 13:53 is xfs good if I have millions of files and thousands of hardlinks? Tomasz Chmielewski
2008-02-19 21:09 ` Peter Grandi
2008-02-19 22:30 ` Mark Goodwin
2008-02-19 22:43   ` Tomasz Chmielewski [this message]
2008-02-20  9:56   ` Tomasz Chmielewski

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=47BB5B8D.2060500@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=markgw@sgi.com \
    --cc=xfs@oss.sgi.com \
    /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