plotly / plotly/dash

provide warnings from dcc.Store depending on data size

Open
#2,123 1 comment 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature P3
Dominant language
Python
Stars
24.4k
Forks
2.3k
Avg merge
2d 7h
Merged PRs (30d)
13

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the dcc.Store implementation and its existing documentation or tests; the issue provides no source file or test entry point. Review the documented browser storage limits, then clarify the warning threshold and supported environments before implementation. Done means developers receive a warning when stored data reaches the agreed size threshold, with coverage for the behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.