On Thu, 23 Mar 2017, Roman Fleysher wrote:
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.
I have been using NFS daily since 1991 and have not seen the problem
you describe. Sometimes such apparent problems are actually due to
improper time synchronization between computers (e.g. using NTP) so
that they don't agree on the time.
The quality of NFS lock managers varies (have improved dramatically
over the many years) and the quality of servers and clients also
varies. A bad NFS server is likely a bad server in general (e.g. does
not synchronously persist data to underlying store when requested). A
bad NFS client tries to improve apparent performance by intentionally
not obeying the rules.
Transaction performance over NFS may not be very good (depending on
properties of server and client) but that does not equate to
corruption or failed locking.
Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
