Live data from Hacker News

Axboe Achieves 8M IOPS Per-Core with Newest Linux Optimization Patches

phoronix.com

51–53 of 53 posts

Re: Axboe Achieves 8M IOPS Per-Core with Newest Linux Optimization Patches

#51
post #40
post #27

He just hit 9M https://twitter.com/axboe/status/1450188650852065291

Anyone know exactly how to replicate this? I see the command line, but it looks like t/io_ring is maybe a wrapper around fio? Or maybe a binary/git repo so I can compile my own?

https://git.kernel.dk/cgit/fio/tree/t/io_uring.c

Re: Axboe Achieves 8M IOPS Per-Core with Newest Linux Optimization Patches

#52
post #47
post #45

Earlier quoted context omitted.

It's FUD to have personally run benchmarks across a number of platforms and machines and have seen very trivial, if any, speedup?

The referenced benchmarks are of poor implementation quality, don't even produce consistent results, and the specific linked issue is rife with discussion better suited to twitter than anything scientific or professional.

Some of the referenced benchmarks are by Jens himself. That's the problem. He has promoted tweets and press releases touting io_uring as being insanely fast when the benchmarks used to come to those conclusions were flawed to begin with.

That's literally the entire point I'm making.

Re: Axboe Achieves 8M IOPS Per-Core with Newest Linux Optimization Patches

#53

Earlier quoted context omitted.

True. But, but, … BUT when it comes to files found on differing (physical/logical/virtual) disk partitions, ye gonna need that block copying mechanism within ‘cp’.

Not necessarily, while reflink works only within the boundaries of the same filesystem there are other optimizations that can operate across filesystems (even networked ones). For example copy_file_range() [1] allows for copy offloading (depending on the underlying fs/storage), which was incidentally also added to coreutils v9.0 [2]. There are also optimizations on other layers, e.g. transparent compression (e.g. btr…

Jen Axboe Rocks!
Post reply on HN