On 26 Jul 2011, at 11:05am, Григорий Григоренко wrote: > This leads us to conclusion: index in SQLITE database if scattered and cannot > be "jumped directly" to N-th element. SQLITE has to read it somehow > consecutively. > > And so SQLITE has to read half of index (!) to find matching index record.
I don't think it's SQLite itself that's reading half the index. I think it's some part of your operating system that's trying to cache all of your database file as SQLite reads lots of different parts of it spread about randomly. Unfortunately I don't see how an OS can reasonably do that since it will produce the slow speeds you're complaining about. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
