Stephen Chrzanowski wrote:
>>From what I understand;
> - Read-Only data
> - Data doesn't change frequently
> - Central repository for data
> - Network latency causing issues
>
> My two cents on this is to keep a database revision ID kicking around and
> do a SQLite backup of the remote data to a
>From what I understand;
- Read-Only data
- Data doesn't change frequently
- Central repository for data
- Network latency causing issues
My two cents on this is to keep a database revision ID kicking around and
do a SQLite backup of the remote data to a local storage medium. At
application
On 2015-04-11 03:30 PM, Peng Yu wrote:
> Hi,
>
> I know that sqlite3 is not recommended to be used on NFS. But I only
> use sqlite3 for read only (the only time that I write is to load the
> initial data to the data base). With this restriction, NFS should be
> fine as the storage since no file
On 11 Apr 2015, at 2:30pm, Peng Yu wrote:
> I am wondering for my limited usage scenario, is it possible to make
> sqlite3 on NFS as fast as sqlite3 on local storage (such as disable
> file locking).
No. Data will flow to a local disk much faster than it can flow across your
network. But
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/11/2015 06:30 AM, Peng Yu wrote:
> I am wondering for my limited usage scenario, is it possible to
> make sqlite3 on NFS as fast as sqlite3 on local storage (such as
> disable file locking).
The latency is what is getting you. SQLite uses
Hi,
I know that sqlite3 is not recommended to be used on NFS. But I only
use sqlite3 for read only (the only time that I write is to load the
initial data to the data base). With this restriction, NFS should be
fine as the storage since no file locking is needed.
I remember that sqlite3 on NFS
6 matches
Mail list logo
