dosubot[bot] commented on issue #34420: URL: https://github.com/apache/superset/issues/34420#issuecomment-3139014504
<!-- Answer --> 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](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/src/dashboard/components/DashboardGrid.jsx)]. 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](https://github.com/apache/superset/issues/33951)]. 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](https://github.com/apache/superset/issues/31799)]. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/9e229976-c1cc-4293-b452-026477652768?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/9e229976-c1cc-4293-b452-026477652768?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/9e229976-c1cc-4293-b452-026477652768?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/9e229976-c1cc-4293-b452-026477652768?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9e229976-c1cc-4293-b452-026477652768?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/9e229976-c1cc-4293-b452-026477652768?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9e229976-c1cc-4293-b452-026477652768?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=githu b) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/34420) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
