Ok resolved the issue. It turns out that the reason because it takes so long is actually due to a default behavior of SQLite. SQLite has a PRAGMA synchronous setting which check that all the data are written correctly to the harddisk after every transaction/operation, therefore taking long time. Turning off the synchronous setting gave me 15-16ms performance with the nested library and less than 1ms performance with the native library. Unfortunately the loss of data on power failure isn't an option for me so I guess I have to live with the 200ms delays.
On Mar 20, 4:26 pm, Xavier RAYNAUD <[EMAIL PROTECTED]> wrote: > Yes, 6-20 ms is perhaps a lot for a single insert. > Note: if I do 1000 inserts inside a BEGIN/COMMIT, it tooks me only 50-80 ms. > > So I think the main part of time is spent on I/O operations. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SQLiteJDBC" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlitejdbc?hl=en -~----------~----~----~----~------~----~------~--~---
