public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Grzegorz Piotr Jaskiewicz <gj@pointblue.com.pl>
To: Anton Blanchard <anton@samba.org>
Cc: Jakob Oestergaard <jakob@unthought.net>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Major XFS problems...
Date: Sat, 11 Sep 2004 20:20:59 +0200	[thread overview]
Message-ID: <4143420B.4040701@pointblue.com.pl> (raw)
In-Reply-To: <20040911133812.GC32755@krispykreme>

Anton Blanchard wrote:

>>In my expierence XFS, was right after JFS the worst and the slowest 
>>filesystem ever made.
>>    
>>
>
>On our NFS benchmarks JFS is _significantly_ faster than ext3 and
>reiserfs. It depends on your workload but calling JFS the worst and
>slowest filesystem ever made is unfair.
>  
>

as always, I am speaking for my own and colegues expierence.
We are using dell SMP machines with p3 and p4, different speeds. Plus 
hardware SCSI raid5's.
For samba, and VoIP services, CVS, and mail. Maybe JFS works nicely with 
NFS, but my expierence shows
that XFS  is the slowest among all filesystems vaillia linux 2.6  can 
serve.  JFS was not so extensively tested, but it doesn't do miracles, 
and expierence shows it's rather close to XFS. Reiserfs so far was the 
finest. Maybe because we have pretty much number of files, mostly small 
ones. I don't know.
I didn't ment to hurt anyone's feelings, just giving my opinion on FSs.

Thanks.

--
GJ

  parent reply	other threads:[~2004-09-11 18:21 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-08 12:35 Major XFS problems Jakob Oestergaard
2004-09-08 15:04 ` Anando Bhattacharya
2004-09-08 15:44   ` Jakob Oestergaard
2004-09-08 16:36     ` Greg Banks
2004-09-08 17:30       ` Jakob Oestergaard
2004-09-09  2:42         ` Greg Banks
2004-09-08 19:06       ` Bill Davidsen
2004-09-09  3:23         ` Greg Banks
2004-09-09 14:00       ` Jakob Oestergaard
2004-09-10  2:40         ` Greg Banks
2004-09-10  3:04           ` Kyle Moffett
2004-09-10  3:24             ` Greg Banks
2004-09-13  7:29         ` Jakob Oestergaard
2004-09-17 11:26           ` [PATCH] " Jakob Oestergaard
2004-09-29 21:45             ` Christoph Hellwig
2004-09-29 22:16               ` Linus Torvalds
2004-09-08 16:16 ` Jan-Frode Myklebust
2004-09-08 21:40 ` Nathan Scott
2004-09-08 23:22   ` Jakob Oestergaard
2004-09-08 23:42     ` Nathan Scott
2004-09-09 12:11       ` Jakob Oestergaard
2004-09-09 18:09         ` Chris Wedgwood
2004-09-11 11:39 ` Grzegorz Piotr Jaskiewicz
2004-09-11 13:03   ` Bjoern Brauel
2004-09-11 13:38   ` Anton Blanchard
2004-09-11 14:54     ` Miquel van Smoorenburg
2004-09-11 18:20     ` Grzegorz Piotr Jaskiewicz [this message]
2004-09-11 13:58 ` Clemens Schwaighofer
  -- strict thread matches above, loose matches on Subject: below --
2004-09-08 13:07 Piszcz, Justin Michael
2004-09-08 13:26 ` Jakob Oestergaard
2004-09-08 15:24 Piszcz, Justin Michael
     [not found] <20040908133954.GB390@unthought.net>
     [not found] ` <20040909074533.B3958243@wobbly.melbourne.sgi.com>
     [not found]   ` <413F823F.3020507@xfs.org>
2004-09-09  6:52     ` Dave Chinner
2004-09-09  8:10       ` Andrew Morton
     [not found] <2Ca3I-2kY-7@gated-at.bofh.it>
     [not found] ` <2Cdl9-4Pc-65@gated-at.bofh.it>
2004-09-11  9:21   ` ADH

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=4143420B.4040701@pointblue.com.pl \
    --to=gj@pointblue.com.pl \
    --cc=anton@samba.org \
    --cc=jakob@unthought.net \
    --cc=linux-kernel@vger.kernel.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