From: Thomas Kaehn <tk@westend.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: xfs@oss.sgi.com
Subject: Re: Strange delete performance using XFS
Date: Thu, 5 Apr 2007 10:17:51 +0200 [thread overview]
Message-ID: <20070405081751.GD2759@mail3b.westend.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0704041012500.7309@p34.internal.lan>
Hi Justin,
On Wed, Apr 04, 2007 at 10:13:36AM -0400, Justin Piszcz wrote:
> I used the DEFAULT create options for XFS as I find it highly optimizes
> itself (at least with SW raid) with the exception of the ROOT FS, I had
> that optimized awhile ago and I kept it:
>
> /dev/md2 / xfs
> logbufs=8,logbsize=262144,biosize=16,noatime,nodiratime,nobarrier 0 1
>
>
> For my regular RAID5s though I use defaults,noatime.
I've disabled barriers, too, and performance increased dramatically.
However I am not aware of the consequences of disabling write barriers.
The FAQ generally recommends using write barriers except when having
a battery-backed cache (this 3ware has not).
| # time for i in `seq 1 100000`; do dd if=/dev/zero of=$i bs=1k count=20 >/dev/null 2>&1; done
|
| real 3m52.182s
| user 0m30.482s
| sys 3m16.152s
|
| # time \rm -rf y
|
| real 0m16.327s
| user 0m0.052s
| sys 0m8.305s
So I am unsure if disabling is an option for me. I could imagine
that write barriers are not properly supported by 3ware or have
to be fine tuned at the kernel or SCSI level.
Ciao,
Thomas
--
Thomas Kähn WESTEND GmbH | Internet-Business-Provider
Technik CISCO Systems Partner - Authorized Reseller
Im Süsterfeld 6 Tel 0241/701333-18
tk@westend.com D-52072 Aachen Fax 0241/911879
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Die Gesellschaft ist eingetragen im Handelsregister Aachen unter HRB 7608
Geschäftsführer: Thomas Neugebauer, Thomas Heller, Michael Kolb
next prev parent reply other threads:[~2007-04-05 8:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 13:05 Strange delete performance using XFS Thomas Kaehn
2007-04-04 13:29 ` Justin Piszcz
2007-04-04 13:47 ` Thomas Kaehn
2007-04-04 13:51 ` Justin Piszcz
2007-04-04 13:57 ` Justin Piszcz
2007-04-04 13:57 ` Justin Piszcz
2007-04-04 14:12 ` Justin Piszcz
2007-04-04 14:21 ` Thomas Kaehn
2007-04-04 14:24 ` Justin Piszcz
2007-04-04 14:35 ` Thomas Kaehn
2007-04-04 20:45 ` Justin Piszcz
2007-04-04 14:13 ` Justin Piszcz
2007-04-05 8:17 ` Thomas Kaehn [this message]
2007-04-04 18:36 ` Justin Piszcz
2007-04-05 7:37 ` Thomas Kaehn
2007-04-04 15:45 ` Chris Wedgwood
2007-04-05 7:28 ` Thomas Kaehn
2007-04-05 9:03 ` Thomas Kaehn
2007-04-05 10:21 ` Justin Piszcz
2007-04-05 10:50 ` Thomas Kaehn
2007-04-05 11:11 ` Justin Piszcz
2007-04-05 15:29 ` Chris Wedgwood
2007-04-06 19:02 ` Peter Grandi
2007-04-11 9:36 ` Thomas Kaehn
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=20070405081751.GD2759@mail3b.westend.com \
--to=tk@westend.com \
--cc=jpiszcz@lucidpixels.com \
--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