From: Emmanuel Florac <eflorac@intellique.com>
To: Songbo Wang <hack.coo@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: about the xfs performance
Date: Mon, 11 Apr 2016 18:10:01 +0200 [thread overview]
Message-ID: <20160411181001.2760439b@harpe.intellique.com> (raw)
In-Reply-To: <CAG=-QKovDGUdLXv9AekeK1o4Dd_bwWNfTTTEcq3VoszBgbmXeQ@mail.gmail.com>
Le Mon, 11 Apr 2016 22:14:06 +0800
Songbo Wang <hack.coo@gmail.com> écrivait:
> mkfs: mkfs.xfs /dev/hioa2 -f -n size=64k -i size=512 -d
> agcount=40 -l size=1024m.
> mount: mount /dev/hioa2 /mnt/ -t xfs -o
> rw,noexec,nodev,noatime,nodiratime,nobarrier,discard,inode64,logbsize=256k,delaylog
> I use the following command to test iops: fio -ioengine=libaio -bs=4k
> -direct=1 -thread -rw=randwrite -size=50G -filename=/mnt/test
> -name="EBS 4KB randwrite test" -iodepth=64 -runtime=60
> The results is normal at the beginning which is about 210k±，but some
> seconds later, the results down to 19k±.
You should first try default mkfs settings, with default mount options.
Normally mkfs.xfs should initiate a TRIM on the SSD, therefore
performance should remain predictable.
What model of SSD card are you using? With an HGST NVMe SN1x0 I've got
very consistent results (no degradation with time).
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-04-11 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 14:14 about the xfs performance Songbo Wang
2016-04-11 16:10 ` Emmanuel Florac [this message]
2016-04-11 19:33 ` Eric Sandeen
2016-04-12 13:27 ` Songbo Wang
2016-04-11 23:10 ` Dave Chinner
2016-04-12 14:07 ` Songbo Wang
2016-04-12 21:31 ` Dave Chinner
2016-04-13 17:27 ` Songbo Wang
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=20160411181001.2760439b@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=hack.coo@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