You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a lot of records which are stored on indexeddb.. in firefox, the size of the indexeddb file is 4.09MB but storing the same data in safari, it is 20.3MB
The text was updated successfully, but these errors were encountered:
Firefox implements the IndexedDB so the shim isn't needed and won't be used. In Safari however there is no implementation of IndexedDB so the shim will be used. This shim uses WebSQL and has to serialize all data on it's on, also it has to keep a system database for storing information like the databases. So there will always be a overhead, but 20.3MB is really big.
It'd be interesting, @axemclion to have a high level understanding of the encoding approach. I wonder whether there are any inefficiencies there that could help this out.
I have a lot of records which are stored on indexeddb.. in firefox, the size of the indexeddb file is 4.09MB but storing the same data in safari, it is 20.3MB
The text was updated successfully, but these errors were encountered: