GitHub user dosubot[bot] added a comment to the discussion: Superset db upgrade is not triggering upgrade
<!-- Answer --> Having a large number of charts and dashboards significantly increases the time and resource usage during a Superset upgrade. Many migration scripts process each dashboard and chart individually—loading, transforming, and committing changes for every record—so the upgrade duration grows with your metadata volume. For example, migrations that convert dashboard layouts or update chart parameters will loop through all dashboards or charts, which can take a long time with thousands of objects. Some migrations even commit after each dashboard, adding overhead for large datasets. This can lead to longer downtime, higher database load, and, in some cases, table locks that impact availability for other users ([details](https://github.com/apache/superset/blob/master/UPDATING.md)). Best practices for large upgrades: always back up your metadata database, schedule the upgrade during a maintenance window, and monitor migration logs for progress. If you notice performance issues after upgrading (for example, with legacy pivot tables), re-saving affected charts can help ([example](https://github.com/apache/superset/issues/31799)). In summary: the more charts and dashboards you have, the longer and more resource-intensive the upgrade will be, so plan accordingly and monitor closely. <!-- 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/2b83af8b-e330-4525-b026-b54083f1dfb2?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/2b83af8b-e330-4525-b026-b54083f1dfb2?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/2b83af8b-e330-4525-b026-b54083f1dfb2?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/2b83af8b-e330-4525-b026-b54083f1dfb2?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/2b83af8b-e330-4525-b026-b54083f1dfb2?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/2b83af8b-e330-4525-b026-b54083f1dfb2?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/2b83af8b-e330-4525-b026-b54083f1dfb2?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=Having%20a%20large%20number%20of%20charts%20and%20dashboards%20significantly%20increases%20the%20time%20and%20resource%20usage%20during%20a%20Superset%20upgrade.%20Many%20migration%20scripts%20process%20each%20dashboard%20and%20chart%20individually%E2%80%94loading%2C%20transforming%2C%20and%20committing%20changes%20for%20every%20record%E2%80%94so%20the%20upgrade%20duration%20grows%20with%20your%20metadata%20volume.%20For%20example%2C%20migrations%20that%20convert%20dashboard%20layouts%20or%20update%20chart%20parameters%20will%20loop%20through%20all%20dashboards%20or%20charts%2C%20which%20can%20take%20a%20long%20time%20with%20thousands%20of%20objects.%20Some%20migrations%20even%20commit%20after%20each%20dashboard%2C%20adding%20overhead%20for%20large%20 datasets.%20This%20can%20lead%20to%20longer%20downtime%2C%20higher%20database%20load%2C%20and%2C%20in%20some%20cases%2C%20table%20locks%20that%20impact%20availability%20for%20other%20users%C2%A0%28%5Bdetails%5D%28https%3A//github.com/apache/superset/blob/master/UPDATING.md%29%29.%0A%0ABest%20practices%20for%20large%20upgrades%3A%20always%20back%20up%20your%20metadata%20database%2C%20schedule%20the%20upgrade%20during%20a%20maintenance%20window%2C%20and%20monitor%20migration%20logs%20for%20progress.%20If%20you%20notice%20performance%20issues%20after%20upgrading%20%28for%20example%2C%20with%20legacy%20pivot%20tables%29%2C%20re-saving%20affected%20charts%20can%20help%C2%A0%28%5Bexample%5D%28https%3A//github.com/apache/superset/issues/31799%29%29.%20%0A%0AIn%20summary%3A%20the%20more%20charts%20and%20dashboards%20you%20have%2C%20the%20longer%20and%20more%20resource-intensive%20the%20upgrade%20will%20be%2C%20so%20plan%20accordingly%20and%20monitor%20closely.) [](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/discussions/37261) GitHub link: https://github.com/apache/superset/discussions/37261#discussioncomment-15545065 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
