3 ms·
The drive controller is internally parallel. The write is just a job queue submission, so the next write hits while it's still processing previous requests.
by monocasa 5y ago
The drive controller is internally parallel. The write is just a job queue submission, so the next write hits while it's still processing previous requests.
- marcan_42 5y agoPeople have tested this stuff on storage devices with torture tests. Can you point at an example of a modern (directly attached) NVMe drive from a reputable vendor that cheats at this? FWIW, macOS also has F_BARRIERFSYNC, which is still much slower than full syncs on the competition.