Bug description
When I edit the dashboard, I find that dragging charts is very slow and often causes the browser to become unresponsive. The deployment environment is k8s, the official deployment method, and the versions are 4.1.1 and 5.0.0. Some screenshots records the proccess
Screenshots/recordings
Superset version
5.0.0
Python version
3.10
Node version
16
Browser
Chrome
Additional context
No response
Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Comment From: dosubot[bot]
Slow dashboard editing and dragging in Superset is a known frontend performance bottleneck, especially for large dashboards. The drag-and-drop system uses React and react-dnd, with throttling on hover events, but in dashboards with many charts, frequent state updates and re-renders can still overwhelm the browser and cause sluggishness or unresponsiveness. There’s no advanced virtualization or batching, so every dashboard item may re-render during drag operations, which is expensive for complex layouts. This is a limitation of the current architecture and not specific to Kubernetes or your deployment method [source].
To mitigate: try reducing the number of charts or components in a single dashboard, split very large dashboards, and close other heavy browser tabs. Make sure your browser and system have enough memory and CPU. If you notice the issue only on certain dashboards, check if they have a particularly large or deeply nested layout.
For diagnosis, use Chrome DevTools’ Performance tab to look for excessive scripting or rendering time, and check the browser console for errors or warnings during drag operations. If you see any specific errors or patterns, sharing those details could help pinpoint the root cause.
There are no recent code changes or config options that address this directly in 4.1.1 or 5.0.0, and no k8s-specific tuning for dashboard editing. Improvements like deeper virtualization or more aggressive throttling would require upstream changes [source].
If you have legacy pivot tables or charts migrated from older Superset versions, try opening and saving them again in the chart editor, as this has resolved some performance issues for others [source].
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other