Agree, it would be pretty nifty! Would not be hard to do, I think the hardest part would actually be the liburing side of it.
Also just generally for development of the aio (on linux using io-uring) patch for postgres. The Samsung 970 Pro I'm currently using for that isn't bad, but it's quite possible to reach its limits. And the performance is a bit too variable over time for benchmarking.
-
-
Did you try overprovisioning the drive (by limiting the available space via either NVME namespacing, or partitioning the pre-defined namespace, if the device doesn't support namespace mgmt)? That solved most performance consistency problems for us with consumer devices.
-
That helped with other disks, but in this case it doesn't seem to be the main problem. I suspect it's a question of how much of the drives internal RAM is available for write caching,, and when it flushes that back.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.