3 ms·
If I recall correctly, this absolutely killed FreeBSD in benchmarks while Linux looked amazing. I recall the editors having to put a note in there saying that L
by nu11ptr 5y ago
If I recall correctly, this absolutely killed FreeBSD in benchmarks while Linux looked amazing. I recall the editors having to put a note in there saying that Linux wasn't committing I/O but FreeBSD was to explain the huge difference. At least I think this is the situation I'm remembering. Hmm..
- fulafel 5y agoThe fsync vs I/O errors bug didn't have any performance impact in absence of failing disks, it was about what happened when you tried to fsync again after your storage stack reported a write error. But for a OS that has a bad fsync, have a look at macOS - they even document that it doesn't commit data to stable storage and you should use some other system call to do it: https://developer.apple.com/library/archive/documentation/System/Conceptual/ManPages_iPhoneOS/man2/fsync.2.html https://developer.apple.com/library/archive/documentation/Sy... (A web search now only finds iOS man pages, but the fsync caveat was the same in OS X/Darwin manpages before they were taken offline)