Skip to content

Storage Overhead

W. "Mac" McMeans edited this page Jul 9, 2022 · 5 revisions

The very nature of storing JavaScript primitives in localStorage involves some extra work. Effectively, this means that a one-byte marker flag is used to track the data type for the key value.

For example, a key value of 3.14159 requires 8 bytes of storage (7 for the value plus 1 for the flag). Where everything is treated as a string, one additional byte per key value stored is the price of maintaining the integrity of the data type.

Memory Keys have no such overhead.

To understand exactly how data is stored and consumed, see the memory requirements.

localStorage Keys

The usual suspects:

set / get      clear      key      remove

The esoteric ones:

Array Keys:
push / pull, pullall      poke      contains      where

Broadcasting:
broadcast

Bypass:
forceset / forceget

Data Transfer:
import / export

Duplicates:
countdupes, showdupes, listdupes

Internals:
cancrunch      crunch / uncrunch

shufflestring / unshufflestring

xorstring

Management:
keys

Memory Consumption:

Memory Quota:
showquota

Query:
haskey, hasval, hastype

Security:
safeset / safeget

setscramblekey / getscramblekey

Type Check:
isarray      isbigint      isboolean      iscrunch

isdate      isfloat      isinteger      isnull

isnumber      isobject      isstring

showtype

Utility:
chopget      copy      softset      rename

Properties:

channel      length      quota      version

Settings:

verbosity

Memory Keys

Standard:

_set / _get      _clear      _key      _remove

Unconventional:

Data Sync:
_backup / _restore

Management:
_keys

Security:
_safeset / _safeget

Type Check:
_isarray      _isbigint      _isboolean      _iscrunch

_isdate      _isfloat      _isinteger      _isnull

_isnumber      _isobject      _isstring

_showtype

Utility:
_chopget      _copy      _softset      _rename

Clone this wiki locally