3 ms·
I understand that to be the case when not using synchronous. The point of synchronous full is that sqlite should only consider a transaction committed when it i
by ryanpetrich 15y ago
I understand that to be the case when not using synchronous. The point of synchronous full is that sqlite should only consider a transaction committed when it is fully flushed to disk. Assuming a 7200rpm disk that isn't lying to you, at most 120 dependent transactions a second should be even possible.
(this should apply equally to other databases that have a similar option)
- MichaelGG 15y agoWhy does the disk need to re-seek to write to the next sector? With things like SQLite WAL, you're just performing sequential writes to disk.
- ryanpetrich 15y agoI hadn't thought of that. If the disk can perform some localized remapping, it's possible to get sequential fsynced writes to exceed the rotation speed.