Optimize app speed

[alyssadai]

Even though the dashboard is now hosted on our cloud server instead of a third-party platform, there is still some noticeable delay when loading and exploring large input tables.

Here are some potential ways to improve the performance:

Ref: https://community.plotly.com/t/slow-rendering-of-large-tables/41596/4

• virtualization=True or pagination (currently employed)
• set debug=False

Ref: https://community.plotly.com/t/slow-load-time-on-dataset/75798/2

• use Patch() to update figs
• part of partial property updates, see also https://dash.plotly.com/partial-properties

Ref: https://community.plotly.com/t/show-and-tell-server-side-caching/42854

• Depends on dash-extensions
• Server-side caching for stores 👀
  • also allows you to use a dataframe directly!!

Refs:

• https://community.plotly.com/t/dash-ag-grid-update-2-0-0rc1-pre-release-is-now-available/73515/50
• https://community.plotly.com/t/dash-ag-grid-open-source/72352
  -> dash-ag-grid

Ref: https://community.plotly.com/t/slow-noticeable-callback-execution-when-updating-multiple-graphs/16739

• using multiple gunicorn workers

Ref: https://community.plotly.com/t/uploading-relatively-small-files-is-taking-too-long-in-dash-plotly/32785/6

• storing + accessing uploaded file contents to a file on the server (rather than using contents as input in callback)

Ref: https://community.plotly.com/t/handling-a-large-csv-file-with-dash-datatable/72428/3

• convert CSV into parquet file first? 🤔

polars instead of pandas?

See also

https://dash.plotly.com/performance
https://dash.plotly.com/dash-enterprise/scale?de-version=5.2
https://strange-quark.medium.com/improving-performance-of-python-dash-dashboards-54547d68f86b

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
  apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
  label in the future. Use sparingly!