From: Eric Sandeen <sandeen@sandeen.net>
To: Stian Jordet <liste@jordet.net>
Cc: Sven-Haegar Koch <haegar@sdinet.de>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Extreme slowness with xfs [WAS: Re: Slowness with new pc]
Date: Tue, 25 Nov 2008 15:22:35 -0600 [thread overview]
Message-ID: <492C6C9B.3060000@sandeen.net> (raw)
In-Reply-To: <1227645887.7992.10.camel@chevrolet>
Stian Jordet wrote:
> ti., 25.11.2008 kl. 01.09 +0100, skrev Sven-Haegar Koch:
>> I had the same problem when I tried it on my laptop (T60) - using it on
>> the unencrypted root filesystem (with /usr/src) took ages, using it on
>> the LUKS encrypted /home was blasing fast - on the same disk.
>>
>> This test was some time ago with something like 2.6.20 or 2.6.24 - I
>> gave up and reformatted / with ext3 as I needed the machine.
>>
>> I think barriers were the problem, they seem to cost performance like
>> hell, especially for operations with many small files. My laptop used
>> barriers for xfs on the direct partition, but not on crypto drivermapper
>> mounts.
>>
>> So perhaps try mounting with nobarrier and see if the speed problem goes
>> away - but know that you sacrifice some crash-resilience when doing so.
>
> Barriers were the problem indeed. My old system had no problems with
> barriers, but here it did an incredible difference.
Depending on the old system, perhaps its storage did not allow the
barriers to be honored, so after xfs saw a test barrier write fail at
mount time, it disabled them ... you'd see a message if that were the
case, FWIW.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2008-11-25 22:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1226760254.5089.11.camel@chevrolet>
[not found] ` <430c4fa50811180551r67d5d680tf1ffa493604ac4ea@mail.gmail.com>
2008-11-23 21:48 ` Extreme slowness with xfs [WAS: Re: Slowness with new pc] Stian Jordet
2008-11-23 22:25 ` Justin Piszcz
2008-11-24 0:19 ` Stian Jordet
2008-11-24 9:50 ` Justin Piszcz
2008-11-24 23:36 ` Stian Jordet
2008-11-24 23:52 ` Justin Piszcz
2008-11-25 0:09 ` Sven-Haegar Koch
2008-11-25 20:44 ` Stian Jordet
2008-11-25 21:22 ` Eric Sandeen [this message]
[not found] ` <1227649893.6557.10.camel@oldsmobile>
2008-11-25 22:02 ` David Sparks
2008-11-25 22:31 ` Stian Jordet
2008-11-25 1:36 ` Eric Sandeen
[not found] ` <1227647010.7992.34.camel@chevrolet>
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=492C6C9B.3060000@sandeen.net \
--to=sandeen@sandeen.net \
--cc=haegar@sdinet.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox