From: Stan Hoeppner <stan@hardwarefreak.com>
To: Hillel Lubman <shtetldik@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: What is a recommended XFS sector size for hybrid (512e) advanced format hard drives?
Date: Mon, 05 Jan 2015 21:21:25 -0600 [thread overview]
Message-ID: <54AB54B5.1020902@hardwarefreak.com> (raw)
In-Reply-To: <11099415.8G4MDk5SIC@shtub-cm>
On 01/05/2015 08:23 PM, Hillel Lubman wrote:
> On Sunday, January 04, 2015 21:52:51 Stan Hoeppner wrote:
>
>> On 01/04/2015 06:56 PM, Hillel Lubman wrote:
>
>> ...
>
>> > when creating XFS partitions on hybrid (512e)
>
>> ...
>
>> > Can you please clarify what after all is the recommended sector size for
>
>> > such drives
>
>> ...
>
>>
>
>> XFS sectsz is unimportant with these drives. What matters is that any
>
>> partitions you create start and end on 4KB boundaries.
>
>
>
> Thanks. So there shouldn't be any negative impact either if sectz is set
> to 4 KB?
Again, as long as your partitions are 4KB aligned.
> In one particular case I experience some perceived slowness on
> 2 TB WD drive (and I created XFS partition on that drive using sectz as
> 4 KB).
Likely due to a misaligned partition. In this case many XFS IOs are
going to cause RMW in two adjacent hardware (4KB) disk sectors as each
XFS block overlaps two sectors. This may significantly hamper drive
performance.
> I didn't test however how it compares to default settings on the
> same drive which would set it to 512 B.
As long as your underlying partition is 4KB aligned the only advantage
you'll likely see with 4B sectsz is a little faster log IO. So for non
metadata heavy workloads you won't see any difference between 512B and
4KB sectsz.
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-01-06 3:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 0:56 What is a recommended XFS sector size for hybrid (512e) advanced format hard drives? Hillel Lubman
2015-01-05 3:52 ` Stan Hoeppner
2015-01-06 2:23 ` Hillel Lubman
2015-01-06 3:21 ` Stan Hoeppner [this message]
2015-01-06 4:01 ` Hillel Lubman
2015-01-06 8:35 ` Matthias Schniedermeyer
2015-01-06 17:02 ` Eric Sandeen
2015-01-06 19:05 ` Chris Murphy
2015-01-06 19:23 ` Eric Sandeen
2015-01-06 19:42 ` Chris Murphy
2015-01-06 19:55 ` Chris Murphy
2015-01-07 5:31 ` Eric Sandeen
2015-01-07 6:01 ` Chris Murphy
2015-01-07 5:17 ` Hillel Lubman
2015-01-07 5:30 ` Eric Sandeen
2015-01-07 5:36 ` Hillel Lubman
2015-01-07 6:06 ` Chris Murphy
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=54AB54B5.1020902@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=shtetldik@gmail.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