All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Stian Jordet <liste@jordet.net>
Cc: xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: Extreme slowness with xfs [WAS: Re: Slowness with new pc]
Date: Mon, 24 Nov 2008 19:36:04 -0600	[thread overview]
Message-ID: <492B5684.2080107@sandeen.net> (raw)
In-Reply-To: <1227569808.5039.6.camel@chevrolet>

Stian Jordet wrote:
> ma., 24.11.2008 kl. 04.50 -0500, skrev Justin Piszcz:
>> While there still may be something else wrong, the first problem I see is 
>> your sunit and swidth are set to 0.
>>
>> Please read, a good article on what they are and how to set them:
>> http://www.socalsysadmin.com/
> 
> Oh, this was new to me. But the setting didn't change anything. I can
> copy one large file between the xfs and ext3 disk (both ways), and I get
> speeds between 160 and 200 MB/s. But unpacking the kernel source takes
> between 5 and 10 minutes on the xfs disk, and a mere 15 seconds on the
> ext3... (and it also used to take between 5 and 10 minutes when I had
> xfs on the raid0, so it doesn't seem to be hardware related...)
> 
> If anyone has anything more I can try before I do the lengthy process of
> backup 1TB, reformat and restore...

I don't know if the storage you're on passes barriers or not, but xfs
has barriers on by default, while ext3 does not.  ext3 will still likely
win the "untar a kernel" race, but for a fairer test, make the barrier
settings consistent between the two.

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: Eric Sandeen <sandeen@sandeen.net>
To: Stian Jordet <liste@jordet.net>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Extreme slowness with xfs [WAS: Re: Slowness with new pc]
Date: Mon, 24 Nov 2008 19:36:04 -0600	[thread overview]
Message-ID: <492B5684.2080107@sandeen.net> (raw)
In-Reply-To: <1227569808.5039.6.camel@chevrolet>

Stian Jordet wrote:
> ma., 24.11.2008 kl. 04.50 -0500, skrev Justin Piszcz:
>> While there still may be something else wrong, the first problem I see is 
>> your sunit and swidth are set to 0.
>>
>> Please read, a good article on what they are and how to set them:
>> http://www.socalsysadmin.com/
> 
> Oh, this was new to me. But the setting didn't change anything. I can
> copy one large file between the xfs and ext3 disk (both ways), and I get
> speeds between 160 and 200 MB/s. But unpacking the kernel source takes
> between 5 and 10 minutes on the xfs disk, and a mere 15 seconds on the
> ext3... (and it also used to take between 5 and 10 minutes when I had
> xfs on the raid0, so it doesn't seem to be hardware related...)
> 
> If anyone has anything more I can try before I do the lengthy process of
> backup 1TB, reformat and restore...

I don't know if the storage you're on passes barriers or not, but xfs
has barriers on by default, while ext3 does not.  ext3 will still likely
win the "untar a kernel" race, but for a fairer test, make the barrier
settings consistent between the two.

-Eric

  parent reply	other threads:[~2008-11-25  1:36 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-15 14:44 Slowness with new pc Stian Jordet
2008-11-18 13:51 ` Sergio Luis
2008-11-23 21:48   ` Extreme slowness with xfs [WAS: Re: Slowness with new pc] Stian Jordet
2008-11-23 21:48     ` Stian Jordet
2008-11-23 22:25     ` Justin Piszcz
2008-11-23 22:25       ` Justin Piszcz
2008-11-24  0:19       ` Stian Jordet
2008-11-24  0:19         ` Stian Jordet
2008-11-24  9:50         ` Justin Piszcz
2008-11-24  9:50           ` Justin Piszcz
2008-11-24 23:36           ` Stian Jordet
2008-11-24 23:36             ` Stian Jordet
2008-11-24 23:52             ` Justin Piszcz
2008-11-24 23:52               ` Justin Piszcz
2008-11-25  0:09             ` Sven-Haegar Koch
2008-11-25  0:09               ` Sven-Haegar Koch
2008-11-25 20:44               ` Stian Jordet
2008-11-25 20:44                 ` Stian Jordet
2008-11-25 21:22                 ` Eric Sandeen
2008-11-25 21:22                   ` Eric Sandeen
2008-11-25 21:51                   ` Stian Jordet
2008-11-25 22:02                     ` David Sparks
2008-11-25 22:31                       ` Stian Jordet
2008-11-25  1:36             ` Eric Sandeen [this message]
2008-11-25  1:36               ` Eric Sandeen
2008-11-25  9:56               ` Justin Piszcz
2008-11-25 10:44                 ` Christoph Hellwig
2008-11-25 10:46                   ` Justin Piszcz
2008-11-25 18:39                 ` Michael Tokarev
2008-11-25 21:03               ` Stian Jordet
2008-11-26 12:30                 ` Martin Steigerwald
2008-11-26 21:43                   ` Dave Chinner

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=492B5684.2080107@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liste@jordet.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.