On 2 Nov 2011, at 4:31pm, Fabian wrote: > 2011/11/2 Mr. Puneet Kishor <punk.k...@gmail.com> > >> Others will have better answers, but methinks that when you reboot the >> computer, the operating system's caches are flushed out, which slows the >> operation. Try working with the db for a bit (SELECT, repeat INSERTs, etc.) >> and notice if the speed increases again to what you expect. > > The reason I reboot the PC for the test, is because I want to have the > caches flushed out, and I fully expect it to make things slower, but not by > the degree (factor 300) i'm experiencing.
Doing lots of inserts under those conditions would require accessing almost every byte of the file. In other words, after your reboot, Windows is probably having to load the entire file into cache again. So let's build that into our expectations. But I agree with Fabian that loading a 150Meg file into cache shouldn't take more than a few seconds. One thing to test is to check to see that Windows is not still doing startup operations while you're doing your testing. Windows presents itself very quickly to the user. It shows a login screen then continues to start many processes in the background. Then once the user is logged in it shows the user their desktop almost immediately, but it hasn't yet started many background operations. If the user immediately starts doing things, they will be slowed down by the fact that the computer hasn't finished starting up yet. So compare your 'restart-and-INSERT' test with one where you restart, log in, then do a few random operations for a minute: start your web browser and load a page. Open and close a few documents or control panels. Sit and do nothing for a minute. /Then/ carry on with the test. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
