4 ms·
In theory the native block size (512 bytes for most drives these days) should be the fastest, but the problem is that if you're doing such small sized I/O, you
by mschuster91 10y ago
In theory the native block size (512 bytes for most drives these days) should be the fastest, but the problem is that if you're doing such small sized I/O, you introduce a shitload of overhead for all the individual r/w calls - I guess that a huge blocksize benefits from DMA and look-ahead reads.
- vmp 10y agoFor some reason I cannot reply to your message directly, only to a parent. Flashbench [1] should be able to tell you what the erase-block and page size is. [1] https://github.com/bradfa/flashbench https://github.com/bradfa/flashbench
- kosma 10y ago> native block size (512 bytes for most drives these days) Not anymore. Advanced Format (4096-byte sector) hard drives have taken the market like a storm, and SSDs benefit even more from using larger I/O sizes (because erase sectors are way larger).
- mschuster91 10y agoAh, I thought it was the other way round. Thanks for the information. Do you know a way to get an SSD's native erase sector size?
- fh973 10y agoIsn't it: the larger the better until you face diminishing returns as with small block sizes the system call overhead becomes noticeable?
- morganvachon 10y agoI've always used bs=4M for writing .iso or .img files to USB flash drives, as it gives me the best times. This is on Linux, OpenBSD, and macOS (using /dev/rdiskn for the latter two).
- koala_man 10y agoWhich theory suggests that this should be the fastest?