From: Milind <milind@gslab.com>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: EXT vs XFS at 80% filled filesystem
Date: Mon, 18 May 2009 18:33:28 +0530 [thread overview]
Message-ID: <1242651808.3339.28.camel@alhena> (raw)
In-Reply-To: <20090430183450.GB19276@mit.edu>
Hi Theodore,
I am facing some weird problem of cross compiling libuuid sources. I
downloaded e2fsprogs and cross-compiled them but when I do "make
install-libs" it doesn't really install libuuid.so but installs
libuuid.a.
Can I have some pointers to build libuuid.so to have it in my toolchain
libraries.
I have crawled through web but couldn't get any nice solution to this.
Thanks in Advance
-Miline
On Thu, 2009-04-30 at 14:34 -0400, Theodore Tso wrote:
> On Thu, Apr 30, 2009 at 01:12:22PM +0530, Milind Dumbare wrote:
> > Hi,
> >
> > I have heard of XFS's performance is not good as compared to EXT3 when
> > the filesystem(disk) is 80% filled with data. Is it true? I have went
> > through lots of performance documents of both XFS and EXT3 but could not
> > find such performance benchmarking (for 80% full filesystems).
>
> I've not heard of any such performance metrics, and I suspect it would
> very much depend on how the filesystem was "aged". A filesystem that
> has been in use for a few years and is at 80% capacity will behave
> very different from a brand-new filesystem which was freshly formatted
> and then filled with a few large files until said filesystem was 80%
> full.
>
> - Ted
>
next prev parent reply other threads:[~2009-05-18 13:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 7:42 EXT vs XFS at 80% filled filesystem Milind Dumbare
2009-04-30 18:34 ` Theodore Tso
2009-05-18 13:03 ` Milind [this message]
2009-05-18 13:17 ` Theodore Tso
2009-05-20 5:43 ` Milind
2009-05-20 10:50 ` Theodore Tso
2009-05-20 11:51 ` Milind
2009-05-20 14:20 ` Theodore Tso
2009-05-20 12:46 ` Matthew Wilcox
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=1242651808.3339.28.camel@alhena \
--to=milind@gslab.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
--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;
as well as URLs for NNTP newsgroup(s).