LiteFS replicates the underlying file system writes by storing the file on a Fuse file system that understands sqlite writes/transactions, it doesn't look like

LiteFS replicates the underlying file system writes by storing the file on a Fuse file system that understands sqlite writes/transactions, it doesn't look like it changes how SQLite runs on top of that file system. The underlying OS page cache is still available, as long as the fuse file system doesn't mess with it [1] so I think this is regular sqlite performance with a fuse overhead to reads/writes. - [0] https://github.com/superfly/litefs/blob/main/docs/ARCHITECTURE.md https://github.com/superfly/litefs/blob/main/docs/ARCHITECTU... - [1] https://github.com/superfly/litefs/issues/149 https://github.com/superfly/litefs/issues/149