Richard Hipp writes: > This is a locality of reference problem. The caching mechanisms (both in > SQLite and in the filesystem of your computer) begins to break down when the > size of the database exceeds available RAM. And when the cache stops > working well, you have to wait on physical I/O which is very slow.
And, of course, this "locality of reference problem" is going to exist no matter what database you use. One might reduce it a bit (even orders of magnitude) using specialized indexes, but it is not something that can be eliminated. So all the references to other databases are just ways to waste ones time. Having said that, let me present a database for consideration: Any filesystem. Split the hex of the MD5 into directory levels and make what you need. Might be slower, particularly with some OSes, but the tools are easy. --David Garfield _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
