Speed up the dashboard
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- data-visualization, performance
Research direction
Start by profiling the dashboard with the 1.6MB and 3.3MB CSV datasets, focusing on initial processing and color-by map selections. Read Dash's performance documentation and compare the mentioned caching, Patch Class, orjson, and clientside callback options. Done means identifying the bottleneck and demonstrating faster loading and map updates without breaking the dashboard.
Written by the indexing model from the issue text.
Description
Currently, the dashboard starts to slow down with datasets at about 1.6MB, this becomes more pronounced by 3.3MB (CSV with about 12,000 rows by 15 columns).
The slow down is most pronounced in
- Initial processing of the dataset (hence we have a loading indicator).
- Selecting different color-by options for the map distribution; the change in the map has a pronounced delay.
Diagnosing the specific source of the slow down (if it's one or more reasons) is still required.
The Dash documentation provides various suggestions under their performance section, and the dash-extensions package also has some options:
- Flask caching. Since the processing is only done once, this would only have potential to speed up the graphing components, though initial testing didn't seem to show improvement.
a. A similar solution is background caching.
b. Dash-extensions has a package for server-side caching: ServersideOutput Transform. This removes the need for JSON serialization between callbacks and should speed things up, though I'm not sure how effective it was (I tried an implementation on the server-store branch). This would also require a regular clean-up of the cached files (as with the previous two). - Dash Patch Class for updating the map (and potentially other graphs as well). Plotly express is fast, but starts to slow down around 15K points (per dash performance docs). I attempted to implement this with the map, but my initial attempt was unsuccessful.
- Using orjson. I'm unclear on precisely how this potential solution works, it seems (and this) that having the package installed allows dash to serialize json strings with orjson instead. There are errors thrown if you try to use it for the serialization (the speedup comes from the fact that it's bytes).
- Clientside Callbacks. To implement this, the graphing portion would have to be translated into Javascript.
- Dominant language
- Python
- Stars
- 6
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Imageomics/dashboard-prototype
-
enhancement help wanted question UX
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
organization
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Filtering QuestionsOpenquestion
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enhancement question
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in Imageomics/dashboard-prototype
Similar issues
-
bug(mcp): handle malformed and partial reranker responses safelyPossibly taken @KamilEjaz890 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
kubeflow/docs-agent#301 ·
Maintainers usually reply within 4 days
-
Update the demo docsOpen
Difficulty 1/5 Under an hour Newbie friendliness 72/100
pulp/pulp_workflow#78 ·
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
pgadmin-org/pgadmin4#10797 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
gcivil-nyu-org/team5-mon-fall26#132 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
gcivil-nyu-org/team4-mon-fall26#291 ·
Maintainers usually reply within 1 day