Versions: dash 3.4.0 (the same code is in 4.4.1), dash-mantine-components 2.5.1, Chromium.
What happens. In selectDashProps, a component whose type sets dashChildrenUpdate calls determineChangedProps(state, strPath). That function iterates Object.entries(state.layoutHashes) and calls isFirstLevelPropsChild, which does two split(',') calls per entry. It does this for every flagged component, on every Redux store update (callback responses, loading-state and request bookkeeping included). layoutHashes gains one entry per path whose props ever changed and never shrinks. So the cost is roughly O(flagged components × changed paths × store updates), and it grows the longer a tab stays open.
Why it bites. DMC sets the flag on MenuItem, MenuDropdown, MenuLabel, SubMenu*, Tooltip, FloatingTooltip, PopoverDropdown, HoverCardDropdown, Stepper and Timeline; dcc sets it on Tabs. An app with a keepMounted header menu (which callbacks inside a closed menu require) and tooltips on navbar links has dozens of flagged components mounted on every page.
Measured (production app; CPU profile via the Chrome DevTools Protocol; headless Chromium; 5 full loads per page):
- The anonymous
isFirstLevelPropsChild comparison was the single hottest function. It took 0.84–2.07 s of main-thread time between a page's layout arriving and its content rendering.
- Deleting
dashChildrenUpdate from the DMC menu and tooltip types before the renderer reads them made page content appear 1.5–2.2× sooner, e.g. 2.83 s → 1.54 s and 5.36 s → 2.56 s. Main-thread busy time fell 3–4×.
- Children inside those components still updated correctly.
Possible fixes:
- Index
layoutHashes by parent path, so a component only looks at its own direct children.
- Or compute the descendant hash once per store update rather than once per flagged component.
- Or let component libraries opt out per type when nothing in the type reads its children's props.
Workaround we use: an inline <head> script, defined before the component bundles load, that traps window.dash_mantine_components and deletes the flag from the menu and tooltip types.
Versions: dash 3.4.0 (the same code is in 4.4.1), dash-mantine-components 2.5.1, Chromium.
What happens. In
selectDashProps, a component whose type setsdashChildrenUpdatecallsdetermineChangedProps(state, strPath). That function iteratesObject.entries(state.layoutHashes)and callsisFirstLevelPropsChild, which does twosplit(',')calls per entry. It does this for every flagged component, on every Redux store update (callback responses, loading-state and request bookkeeping included).layoutHashesgains one entry per path whose props ever changed and never shrinks. So the cost is roughly O(flagged components × changed paths × store updates), and it grows the longer a tab stays open.Why it bites. DMC sets the flag on
MenuItem,MenuDropdown,MenuLabel,SubMenu*,Tooltip,FloatingTooltip,PopoverDropdown,HoverCardDropdown,StepperandTimeline; dcc sets it onTabs. An app with akeepMountedheader menu (which callbacks inside a closed menu require) and tooltips on navbar links has dozens of flagged components mounted on every page.Measured (production app; CPU profile via the Chrome DevTools Protocol; headless Chromium; 5 full loads per page):
isFirstLevelPropsChildcomparison was the single hottest function. It took 0.84–2.07 s of main-thread time between a page's layout arriving and its content rendering.dashChildrenUpdatefrom the DMC menu and tooltip types before the renderer reads them made page content appear 1.5–2.2× sooner, e.g. 2.83 s → 1.54 s and 5.36 s → 2.56 s. Main-thread busy time fell 3–4×.Possible fixes:
layoutHashesby parent path, so a component only looks at its own direct children.Workaround we use: an inline
<head>script, defined before the component bundles load, that trapswindow.dash_mantine_componentsand deletes the flag from the menu and tooltip types.