Is lovefield good for big data storage of 3GB or so?

[ta...@izap.in]

Hi Guys,

We are trying to build some desktop application by using electron + Local Database. Where lovefield seems to me good choice. We would have data storage up to 3GB. So is lovefield a good choice especially when i've seen indexeddb has limit of 50MB.

Thank you.

Tarun Jangra

[dpa...@chromium.org]

Unfortunately no. Lovefield currently has a (signifacant) limitation that all data is kept in an in-memory cache. This is OK for a very large number of use cases (mostly for web sites which hold much less data).

Perhaps a viable alternative:

Were you planning on storing blobs/arraybuffers in Lovefield? You could instead only store metadata about your blobs/arraybuffers in Lovefield, and place the actual files in some other persistent storage. This approach has already been used by some Lovefield clients (where https://developer.chrome.com/apps/fileSystem API was used for storing videos).

This way you could reduced the size of the data stored within Lovefield and perhaps then it would be usable for your use case.

I hope this helps

[Tarun Jangra]

Thank you to return back to me. Since i'm not planning to store blobs/arraybuffers in Lovefield so case study of saving video in the fileSystem API is not pretty useful for my case. Actually we are building some POS installable on desktop. Where some of the specific tables will remain on local machine and some will work with web API. So i'm trying to find something relevant.   

[lekhi...@gmail.com]

Hey, I came across the same issue, which database did you guys end up using?

Thanks for your help in advance. 

[graha...@gmail.com]

I recently; using the CORDOVA Android environment to develop a 1D/2D application - ran into a problem when loading master data of some 11,000 rows 120 byte rows to find that when retrieving keys beyond (I think row 5,000 position), the request returned not found.

The raw data size uploaded to populate the DB was far less than 1 GIG

No error exceptions were reported during the DB build process

With a lesser, under 2,000 rows, it worked fine

I replaced the LoveField persistence part with SQLITE & works flawlessly.

Unfortunately, due to production demands, I needed to move away from LoveField despite the nice way in which it works