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: Thu, 15 Oct 2020 06:43:40 +0800 [thread overview]
Message-ID: <20201015064339.35D4.409509F4@e16-tech.com> (raw)
In-Reply-To: <20201014212458.GC7391@dread.disaster.area>
Hi,
> Reads can still be served from the page cache without doing physical
> IO.
You are right.
for ext4, with more clients(32->80), the Throughput of ext4 is over
6Gb/s too.
the 'Throughput' of dbench include not only 'write', but also include
'read' in dbench too.
And 'max_latency' include not only 'write', but also include others too.
1)dbench result example1
WriteX 365460 4.474 2279.808
...
Throughput 385.697 MB/sec (sync open) 32 clients 32 procs max_latency=2279.818 ms
2)dbench result example2
WriteX 741543 3.521 16.380
...
Throughput 779.972 MB/sec (sync open) 48 clients 48 procs max_latency=11.246 ms
Thanks a lot.
Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2020/10/15
prev parent reply other threads:[~2020-10-14 22:43 UTC|newest]
Thread overview: 5+ 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
2020-10-14 21:24 ` Dave Chinner
2020-10-14 22:43 ` Wang Yugui [this message]
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=20201015064339.35D4.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).