From: Stian Jordet <liste@jordet.net>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Stian Jordet <liste@jordet.net>,
Sven-Haegar Koch <haegar@sdinet.de>,
xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: Extreme slowness with xfs [WAS: Re: Slowness with new pc]
Date: Tue, 25 Nov 2008 22:51:33 +0100 [thread overview]
Message-ID: <1227649893.6557.10.camel@oldsmobile> (raw)
In-Reply-To: <492C6C9B.3060000@sandeen.net>
ti., 25.11.2008 kl. 15.22 -0600, skrev Eric Sandeen:
> 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.
I know those messages, I get them on my old server. But my old
workstation did not disable the barrier...
But I still don't understand this. On my laptop (HP EliteBook 8530w,
very very powerful, but still a laptop, not an eight core, hardware raid
workstation...), I get this (xfs partition):
barrier:
time bash -c 'tar xjf linux-2.6.27.7.tar.bz2; sync'
real 1m30.855s
user 0m23.265s
sys 0m4.096s
nobarrier:
time bash -c 'tar xjf linux-2.6.27.7.tar.bz2; sync'
real 0m37.602s
user 0m15.281s
sys 0m4.184s
With no barriers, it's 22s faster than my workstation. That can't be the
way it's supposed to be?
-Stian
next prev parent reply other threads:[~2008-11-25 21:51 UTC|newest]
Thread overview: 18+ 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 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
2008-11-25 21:51 ` Stian Jordet [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
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=1227649893.6557.10.camel@oldsmobile \
--to=liste@jordet.net \
--cc=haegar@sdinet.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@sandeen.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