I do not have big experience in the area, but have some. I think that light weight use is not the right thing to ask. I have seen NFS delays of 20 seconds: file was created on one machine and showed up on another after 20 seconds. This depends on how heavy OTHER things are, not how heavy SQLite access is.
GFS2 and GPFS supposedly solve file synchronization issue (by sharing disk inodes rather than files ). I never tested this (we have GPFS) and do not know about other file systems. Roman ________________________________________ From: sqlite-users [[email protected]] on behalf of Simon Slavin [[email protected]] Sent: Thursday, March 23, 2017 2:14 PM To: SQLite mailing list Subject: Re: [sqlite] Developing a SQLite3 DB remotely On 23 Mar 2017, at 5:45pm, Stephen Chrzanowski <[email protected]> wrote: > The remote > system is a Linux based OS. […] How 'remote' is this ? What protocol is used to do the remote access ? > What would be a recommended way to setup the > connections for a DEV-only arena where the below paragraph describes? … or is that what you’re asking for advice on here ? > By EXTREMELY LIGHT WEIGHT use, I mean I *DO* guarantee that although I have > one permanent open file handle to the database via SEP, and that Linux OS > will only open a handle periodically while I'm writing the script, > multiple accesses of reading or writing to the DB at the exact same time > just will not happen. Set a timeout of at least 10 seconds on all connections to the database. Apart from that I can’t think of anything you haven’t mentioned. I do more complicated things by using SQLite as a back end to a web-facing system without problems. Simon. _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
