Fresh Take On Linux Uncached Buffered I/O "RWF_UNCACHED" Nets 65~75% Improvement

[aviallon]

So, probably marginal and negligible gains for the average user.

I hit the exact same problem on my hypervisors, which is why every VM disk is configured so that it bypasses the host's page cache (even when it could improve performance a lot).
This would mean a lot of free performance for me. Especially since this is self-hosting, and I do not have much money lol.

[Anon'ym']

And yes it will benifit the average user it will probably be in the range from 3-5% improvement but it helps.

In days where your average user has ssd that can give you 500 mbits even if you use a sata ssd you will see an increase of 25 mbits as conservative estimation, not to mention nvmes that run with 3gbits or pcie4 that run at 5 gbits, at 5gbits it already means a gain of 250mbits ~~.

ONLY if application will use this specific devs dont know about they exist flags?

[Anon'ym']

You mean desktop user? Probably yes.
But if you are a customer using some services, you'd be happy to see it's speed boosted up.

It will not. Maybe you will get even more telemetry.

[coder]

It would be interesting to see a phoronix benchmark comparison with these patches.

I think it requires a code modification to actually use his new method. Unless you can just 1:1 replace code using O_DIRECT with this new flag, I doubt there will be anything to benchmark until the patches land and a few intrepid developers of I/O-heavy packages decide to start using it.

And yes it will benifit the average user it will probably be in the range from 3-5% improvement but it helps.

It's highly dependent on using software which wants uncached I/O. The main uses cases for this are related to media streaming and things like databases that do their own caching. Normal userspace code shouldn't use this, just as they don't currently use O_DIRECT.

Yes, O_DIRECT is more painful and annoying, which is the point of this new flag. However, most packages that have stood to benefit from uncached I/O are already using that method.

I wonder if this new flag has a performance benefit vs. O_DIRECT, or if its main benefits mostly fall in the category of ease-of-use and fewer caveats. I think it's telling that he didn't benchmark it against O_DIRECT.

[Svyatko]

In days where your average user has ssd that can give you 500 mbits even if you use a sata ssd you will see an increase of 25 mbits as conservative estimation, not to mention nvmes that run with 3gbits or pcie4 that run at 5 gbits, at 5gbits it already means a gain of 250mbits ~~.

Ah thats a general asumption ofc you cant exeed the bus speeds sata 600mbit pci3x4 4gbits pcix4x4 8gbits.

Bytes, not bits.
SATA provides 600 MB/s = 600 megabytes/s.
For PCIe 5 consumer SSDs we have 4 lanes * 4 GB/s = 16 GB/s in one direction, it is possible to transfer data up & down simultaneously.

[coder]

SATA provides 600 MB/s = 600 megabytes/s.

The standard stipulates 6 Gbps, however the fastest SATA SSDs seem to top out around 550 MB/s in sequential reads.

For PCIe 5 consumer SSDs we have 4 lanes * 4 GB/s = 16 GB/s in one direction, it is possible to transfer data up & down simultaneously.

Eh, PCIe 5-based consumer SSDs burn quite a lot of power, though. I doubt any will sustain those speeds, either. And a mixed workload (read+write) is still going to be bottlenecked by the underlying NAND chips, which can either read or write, but not both simultaneously.

[Svyatko]

The standard stipulates 6 Gbps, however the fastest SATA SSDs seem to top out around 550 MB/s in sequential reads.

https://en.wikipedia.org/wiki/SATA#SATA_revision_3.0_(6_Gbit/s,_600_MB/s,_Serial_ATA-600)

Third-generation SATA interfaces run with a native transfer rate of 6.0 Gbit/s; taking 8b/10b encoding into account, the maximum uncoded transfer rate is 4.8 Gbit/s (600 MB/s).

Eh, PCIe 5-based consumer SSDs burn quite a lot of power, though. I doubt any will sustain those speeds, either. And a mixed workload (read+write) is still going to be bottlenecked by the underlying NAND chips, which can either read or write, but not both simultaneously.

Drive controller can read data from NAND chip in one channel, and write data to another chip in another channel.
Also 2 TB SSD NVMe drive can use 2 - 4 GiB onboard DRAM cache, and combine reading from it with writing to it plus using NAND chips, and using SLC cache on NAND chips.