-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rich Rattanni wrote: > This seems to take a great deal of > time so instead I thought abou having the database do an integrity > check at powerup, however this too takes a great deal of time.
Couldn't you go ahead and do your quick check on startup and then do the integrity check later when the database is otherwise unoccupied? If your database is smaller than system memory then there is also value in just reading the entire file so that it is cached by the OS which will cause initial queries to be a lot quicker because they won't have to page in things from disk. If you look at your timing figures you can see that the integrity check and md5sum are spending all their time in system - ie reading the file into memory. You may find a more effective way of reading into memory using appropriate block sizes, asynchronous I/O etc. You can also tweak SQLite block sizes to match OS block sizes. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIVxm5mOOfHg372QQRAj5dAJ0bOWxUKVN0SsEIk/ESrRDBTJtkjgCffyG/ Yo4WR6YTD3qb5u3lTaL7ivU= =Bn+D -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
