From: Wang Yugui <wangyugui@e16-tech.com>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: dbench throughput on xfs over hardware limit(6Gb/s)
Date: Wed, 14 Oct 2020 11:32:11 +0800 [thread overview]
Message-ID: <20201014113211.2372.409509F4@e16-tech.com> (raw)
In-Reply-To: <20201013230521.GB7391@dread.disaster.area>
> On Tue, Oct 13, 2020 at 10:11:13PM +0800, Wang Yugui wrote:
> > Hi,
> >
> > dbench throughput on xfs over hardware limit(6Gb/s=750MB/s).
> >
> > Is this a bug or some feature of performance optimization?
>
> dbench measures page cache throughput, not physical IO throughput.
> This sort of results is expected.
We use 'dbench -s', so it should be physical IO.
-s Use synchronous file IO on all file operations.
we check 'dbench -s' with 'strace -ff -o s.log',
we can see 'O_SYNC' in openat().
Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2020/10/14
next prev parent reply other threads:[~2020-10-14 3:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 14:11 dbench throughput on xfs over hardware limit(6Gb/s) Wang Yugui
2020-10-13 23:05 ` Dave Chinner
2020-10-14 3:32 ` Wang Yugui [this message]
2020-10-14 21:24 ` Dave Chinner
2020-10-14 22:43 ` Wang Yugui
-- strict thread matches above, loose matches on Subject: below --
2020-10-13 14:09 Wang Yugui
2020-10-13 14:13 ` Wang Yugui
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=20201014113211.2372.409509F4@e16-tech.com \
--to=wangyugui@e16-tech.com \
--cc=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
/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.