|
|
|
|
|
|
by LAC-Tech
337 days ago
|
|
|
Great article, but I have a question: The problem with naive async I/O in a database context at least, is that you lose the durability guarantee that makes databases useful. When a client receives a success response, their expectation is the data will survive a system crash. But with async I/O, by the time you send that response, the data might still be sitting in kernel buffers, not yet written to stable storage. Shouldn't you just tie the successful response to a successful fsync? Async or sync, I'm not sure what's different here. |
|
|