From: Eric Sandeen <sandeen@sandeen.net>
To: Shrinand Javadekar <shrinand@maginatics.com>, xfs@oss.sgi.com
Subject: Re: Performance impact of mkfs.xfs vs mkfs.xfs -f
Date: Tue, 25 Aug 2015 16:44:47 -0500 [thread overview]
Message-ID: <55DCE1CF.5030708@sandeen.net> (raw)
In-Reply-To: <CABppvi6GdaTQgqpYJi6RhkpjP9ydTV8-2VV8LF9tHSN63XzWtA@mail.gmail.com>
On 8/25/15 3:32 PM, Shrinand Javadekar wrote:
> Hi,
>
> I have 23 disks formatted with XFS on a single server. The workload is
> Openstack Swift. See this email from a few months ago about the
> details:
>
> http://oss.sgi.com/archives/xfs/2015-06/msg00108.html
>
> I am observing some strange behavior and would like to get some
> feedback about why this is happening.
>
> I formatted the disks with xfs (mkfs.xfs) and deployed Openstack Swift
> on it. Writing 100GB of data into Swift in batches of 20GB each gave
> us the following throughput:
>
> 20 GB: 93MB/s
> 40 GB: 65MB/s
> 60 GB: 52MB/s
> 80 GB: 50MB/s
> 100 GB: 48MB/s
>
> I then re-formatted the disks with mkfs.xfs -f and ran the experiment
> again. This time I got the following throughput:
>
> 20 GB: 118MB/s
> 40 GB: 95MB/s
> 60 GB: 74MB/s
> 80 GB: 68MB/s
> 100 GB: 63MB/s
>
> I've seen similar results twice.
How did you do the above twice, out of curiosity? If it's the same set of disks,
the 3rd mkfs would require "-f" to overwrite the old format.
> Any ideas why this might be happening?
With the paucity of information you've provided, nope!
What version of xfsprogs are you using?
What was the output of mkfs.xfs each time; did the geometry differ?
-f sets force_overwrite, which only does 3 things:
1) overwrite existing filesystem signatures
3) zeros out old xfs structures on disk
2) allow mkfs to proceed on a misaligned device
I don't see why any of those behaviors would change runtime behavior.
Maybe you have other variables in your performance testing, and two
tests isn't enough to sort out noise?
-Eric
> Thanks in advance.
> -Shri
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-08-25 21:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 20:32 Performance impact of mkfs.xfs vs mkfs.xfs -f Shrinand Javadekar
2015-08-25 21:24 ` Shrinand Javadekar
2015-08-25 21:44 ` Eric Sandeen [this message]
2015-08-25 23:09 ` Shrinand Javadekar
2015-08-25 23:43 ` Dave Chinner
2015-08-26 0:39 ` Carlos E. R.
2015-08-26 1:09 ` Dave Chinner
2015-08-26 7:25 ` Martin Steigerwald
2015-08-26 17:48 ` Shrinand Javadekar
2015-08-26 18:44 ` Eric Sandeen
2015-08-26 19:04 ` Eric Sandeen
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=55DCE1CF.5030708@sandeen.net \
--to=sandeen@sandeen.net \
--cc=shrinand@maginatics.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.