From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: XFS: Abysmal write performance because of excessive seeking (allocation groups to blame?)
Date: Mon, 09 Apr 2012 00:27:29 -0500 [thread overview]
Message-ID: <4F827341.2000607@hardwarefreak.com> (raw)
In-Reply-To: <20120408234555.695e291f@galadriel.home>
On 4/8/2012 4:45 PM, Emmanuel Florac wrote:
> Le Sun, 08 Apr 2012 15:33:01 -0500 vous écriviez:
>
>>>
>>> From my experience, with modern arrays don't make much of a
>>> difference. I've reached decent IOPS (i. e. about 4000 IOPS) on
>>> large arrays of up to 46 drives provided there are enough threads
>>> -- more threads than spindles, preferably.
>>
>> Are you speaking of a mixed metadata/data heavy IOPS workload similar
>> to that which is the focus of this thread, or another type of
>> workload? Is this 46 drive array RAID10 or RAID6?
>
> Pure random access, 8K IO benchmark (database simulation). RAID-6
> performs about the same in pure reading tests, but stinks terribly at
> writing of course.
In your RAID10 random write testing, was this with a filesystem or doing
direct block IO? If the latter, I wonder if its write pattern is
anything like the access pattern we'd see hitting dozens of AGs while
creating 10s of thousands of files.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-04-09 5:27 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 18:10 XFS: Abysmal write performance because of excessive seeking (allocation groups to blame?) Stefan Ring
2012-04-05 19:56 ` Peter Grandi
2012-04-05 22:41 ` Peter Grandi
2012-04-06 14:36 ` Peter Grandi
2012-04-06 15:37 ` Stefan Ring
2012-04-07 13:33 ` Peter Grandi
2012-04-05 21:37 ` Christoph Hellwig
2012-04-06 1:09 ` Peter Grandi
2012-04-06 8:25 ` Stefan Ring
2012-04-07 18:57 ` Martin Steigerwald
2012-04-10 14:02 ` Stefan Ring
2012-04-10 14:32 ` Joe Landman
2012-04-10 15:56 ` Stefan Ring
2012-04-10 18:13 ` Martin Steigerwald
2012-04-10 20:44 ` Stan Hoeppner
2012-04-10 21:00 ` Stefan Ring
2012-04-05 22:32 ` Roger Willcocks
2012-04-06 7:11 ` Stefan Ring
2012-04-06 8:24 ` Stefan Ring
2012-04-05 23:07 ` Peter Grandi
2012-04-06 0:13 ` Peter Grandi
2012-04-06 7:27 ` Stefan Ring
2012-04-06 23:28 ` Stan Hoeppner
2012-04-07 7:27 ` Stefan Ring
2012-04-07 8:53 ` Emmanuel Florac
2012-04-07 14:57 ` Stan Hoeppner
2012-04-09 11:02 ` Stefan Ring
2012-04-09 12:48 ` Emmanuel Florac
2012-04-09 12:53 ` Stefan Ring
2012-04-09 13:03 ` Emmanuel Florac
2012-04-09 23:38 ` Stan Hoeppner
2012-04-10 6:11 ` Stefan Ring
2012-04-10 20:29 ` Stan Hoeppner
2012-04-10 20:43 ` Stefan Ring
2012-04-10 21:29 ` Stan Hoeppner
2012-04-09 0:19 ` Dave Chinner
2012-04-09 11:39 ` Emmanuel Florac
2012-04-09 21:47 ` Dave Chinner
2012-04-07 8:49 ` Emmanuel Florac
2012-04-08 20:33 ` Stan Hoeppner
2012-04-08 21:45 ` Emmanuel Florac
2012-04-09 5:27 ` Stan Hoeppner [this message]
2012-04-09 12:45 ` Emmanuel Florac
2012-04-13 19:36 ` Stefan Ring
2012-04-14 7:32 ` Stan Hoeppner
2012-04-14 11:30 ` Stefan Ring
2012-04-09 14:21 ` Geoffrey Wehrman
2012-04-10 19:30 ` Stan Hoeppner
2012-04-11 22:19 ` Geoffrey Wehrman
2012-04-07 16:50 ` Peter Grandi
2012-04-07 17:10 ` Joe Landman
2012-04-08 21:42 ` Stan Hoeppner
2012-04-09 5:13 ` Stan Hoeppner
2012-04-09 11:52 ` Stefan Ring
2012-04-10 7:34 ` Stan Hoeppner
2012-04-10 13:59 ` Stefan Ring
2012-04-09 9:23 ` Stefan Ring
2012-04-09 23:06 ` Stan Hoeppner
2012-04-06 0:53 ` Peter Grandi
2012-04-06 7:32 ` Stefan Ring
2012-04-06 5:53 ` Stefan Ring
2012-04-06 15:35 ` Peter Grandi
2012-04-10 14:05 ` Stefan Ring
2012-04-07 19:11 ` Peter Grandi
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=4F827341.2000607@hardwarefreak.com \
--to=stan@hardwarefreak.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