cristiant / litedbvssqlite Goto Github PK

Hi,

Every single Insert in your loop actually triggers a begin -> insert -> commit sequence, and transactions "are atomic, consistent, isolated, and durable" [1] - so by forcing the engine to do a commit after every single insert you force the engine to guarantee the ACID state, involving a full sync to disc and everything else needed for ACID, one million times in a row.

In order to get a meaningful benchmark you would have to do something like this:

db.Begin(); for(int i = 0; i < 1000000; i++) { /*insert*/ } db.Commit();

[1] https://sqlite.org/features.html