dbench throughput on xfs over hardware limit(6Gb/s)
Hi,
dbench throughput on xfs over hardware limit(6Gb/s=750MB/s).
Is this a bug or some feature of performance optimization?
Disk: TOSHIBA PX05SMQ040
This is a 12Gb/s SAS SSD disk, but connect to 6Gb/s SAS HBA, so it works with 6Gb/s.
dbench -s -t 60 -D /xfs 32
#Throughput 884.406 MB/sec (sync open)
dbench -s -t 60 -D /xfs 1
#Throughput 149.172 MB/sec (sync open)
we test the same disk with ext4 filesystem,
the throughput is very close to, but less than the hardware limit.
dbench -s -t 60 -D /ext4 32
#Throughput 740.95 MB/sec (sync open)
dbench -s -t 60 -D /ext4 1
#Throughput 124.67 MB/sec (sync open)
linux kernel: 5.4.70, 5.9.0
Best Regards
王玉贵
2020/10/13
--------------------------------------
北京京垓科技有限公司
王玉贵 [email protected]
电话:+86-136-71123776
Quoted 5 lines · Wang Yugui
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.
Cheers,
Dave.
Signature · 2 lines
Dave Chinner [email protected]
Quoted 10 lines · Wang Yugui
Quoted 5 lines
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 ([email protected])
2020/10/14
Quoted 6 lines · Wang Yugui
Quoted 6 lines · Wang Yugui
Quoted 4 lines
Hi,
dbench throughput on xfs over hardware limit(6Gb/s=750MB/s).
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
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.
Reads can still be served from the page cache without doing physical IO.
Cheers,
Dave.
Signature · 2 lines
Dave Chinner [email protected]
Hi,
Quoted 2 lines
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 ([email protected])
2020/10/15