Have you checked the options that are set for the Hard Drive Controller and Drives? (Particularly the ones that disable OS and hardware cache flushing).
Perhaps Windows 7 drivers are doing an fsync when fync is called. 120 ms per transaction is pretty good for a machine that is working properly. 1 or 2 ms per transaction is physically impossible on rotating disk. > -----Original Message----- > From: sqlite-users-bounces at mailinglists.sqlite.org [mailto:sqlite-users- > bounces at mailinglists.sqlite.org] On Behalf Of Lucas Ratusznei Fonseca > Sent: Saturday, 17 October, 2015 13:53 > To: sqlite-users at mailinglists.sqlite.org > Subject: [sqlite] Sqlite good on Windows XP but very very slow on Windows > Seven > > Hi all, > > I am using sqlite for years with my software on Windows XP, no more than 1 > or 2 milliseconds per transaction (insert), so speed has never been a > concern. Until now. > I had to migrate my system to Windows Seven recently, I am still doing > tests and stuff. It happens that some processes became very slow. Digging > in the source code, I found out that Sqlite transactions now take about > 120 > milliseconds, which is unacceptable for me. > I tried to modify journaling and synchronization, I achieved great time > reduction but not enough. Besides, I must not change journaling and sync > because of integrity. I need it to work well with the defaults. > Is there something I am missing? > > Best regards > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
