-
-
Notifications
You must be signed in to change notification settings - Fork 16
LocalStorage Speed
The data from localStorage is stored in an SQLite database on the user's filesystem. Read operations are generally considered very quick.
Some benchmarks compare the speed of disk-based IO to the efficiency of reading and writing to memory. Even with SSD hardware, how will any filesystem be comparable to direct memory? In automotive terms, it's like comparing the performance of a Chevy Chevette to a Lamborghini, and then railing at the Chevette for being slower.
How could it be otherwise?
If the raw speed of localStorage by itself is unsatisfactory, you'll get no further joy using locaDataStorage. The convenience factor of data type tracking, string compression, etc. comes at a cost, and read/write times will be minimally slower compared to using the native API without a wrapper.
For ultimate speed, localDataStorage lets you use Memory Keys. However, change events are not triggered.
Array Keys:
push / pull, pullall poke contains where
Broadcasting:
broadcast
Data Transfer:
import / export
Duplicates:
countdupes, showdupes, listdupes
Internals:
cancrunch crunch / uncrunch
shufflestring / unshufflestring
Management:
keys
Memory Consumption:
Memory Quota:
showquota
Query:
haskey, hasval, hastype
setscramblekey / getscramblekey
Type Check:
isarray isbigint isboolean iscrunch
isdate isfloat isinteger isnull
Utility:
chopget copy softset rename
_set / _get _clear _key _remove
Management:
_keys
Type Check:
_isarray _isbigint _isboolean _iscrunch