On Thu, Feb 07, 2013 at 04:11:18PM +0100, Eduardo Morras scratched on the wall:
> If you need cache being persistent between process on the same server, > you can build a ram disk, write the db there and use it from any > process. This way you read the db only once from nfs. Even better, you > can shutdown nfs because a simple ftp/http server and wget/fetch can > do what you want, serve/receive read only files. It would be more straight forward to just have SQLite create an in-memory database, and then use the backup APIs to copy the central database to the in-memory database. Once that was done, all requests could be serviced out of the in-memory database. In this way, the database would always be in process memory, with no dependencies on either the NFS link (after load) or the file-system cache. It would also require a very minimal number of changes to the process code. -j -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Intelligence is like underwear: it is important that you have it, but showing it to the wrong people has the tendency to make them feel uncomfortable." -- Angela Johnson _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
