-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Description
The docs for dcc.Store
note (at the very bottom):
The maximum browser storage space is determined by the following factors:
Mobile or laptop
The browser, under which a sophisticated algorithm is implemented within Quota Management
Storage encoding where UTF-16 can end up saving only half of the size of UTF-8
It's generally safe to store up to 2MB in most environments, and 5~10MB in most desktop-only applications.
modified_timestamp is read only.
There are clear and quite low storage limitations, but for the developer it is not obvious that dcc.Store
is a "use don't abuse" component unless they know these docs well. I've seen many cases of developers working with dcc.Store
and dumping massive datasets into it without realizing the practical implications of this.
It would be great if dcc.Store
had some monitor for the size of data being passed to it and could raise a warning to the developer that they might consider other options to support caching data once it reaches a certain threshhold.