4 ms·
I've seen this show before. Let's async all the things IO and not pay attention to database integrity and reliably fsync'ing with storage. I look forward to drh
by sqliteoldtimr 2y ago
I've seen this show before. Let's async all the things IO and not pay attention to database integrity and reliably fsync'ing with storage. I look forward to drh's rebuttal.
- hinkley 2y agoJepsen will have interesting things to say as well.
- adgjlsfhk1 2y agoIIUC this is only about read performance. It's totally fine to async all your reads as long as (like SQLite does) you have a Reader-Writer lock and verify integrity properly on writes.
- avinassh 2y ago> Let's async all the things IO and not pay attention to database integrity and reliably fsync'ing with storage I am not sure how does this affect database integrity or reliably fsync-ing for e.g. TigerBeetle is another rock solid database which uses async IO. I mentioning it because it is way more mature than Limbo and does a great job at durability