The purpose of a cache is to improve performance and responsiveness. Any cache that uses all physical memory, forces all other apps to the paging file and turns the operating system into a brick is definitely not working as designed.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roger Binns Sent: Wednesday, September 17, 2008 1:18 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] Vista frustrations -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Robert Simpson wrote: > To me this seems like an obvious bug in Vista, Actually I'd argue that it is behaving as designed. Generally filesystem code will try to detect what is going on under the hood. In particular if it looks like you are doing sequential access(*) then they will start doing read ahead, whereas read ahead is a waste for random access. By using the sequential or random flags you are explicitly telling the filesystem to ignore its heuristics and do as you say only. Since SQLite cannot tell in advance whether access is almost entirely random or almost entirely sequential, it makes far more sense to let the operating system use its builtin heuristics and optimise accordingly. (*) Sun's ZFS can even detect strided sequential access - ie reading X amount of data every Y kilobytes. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFI0L0vmOOfHg372QQRAk+7AKCEloS0d+xB+M2C/Bap38ilZZ8tVACfciC4 vMfbYMNVV9k6CNR7hpSQo6A= =AXGU -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list firstname.lastname@example.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list email@example.com http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users