Roadmap 0.11, Fixes
FX.46 Apps start slowly since 0.8.1: the app bar re-measured on every change, Settings panels built at load, BimCraft massing and ModelCraft swatches ran at start
Several users and the owner saw every app start slower after the 0.8.1 changes. Measured headless (CadCraft, pinned builds, networkidle): 0.7.1 about 1.3 s, 0.8 about 1.8 to 2.2 s, 0.8.1 about 2.2 to 2.8 s; main-thread busy time 490 ms, 780 ms, 820 ms.
Found with a CPU profile of the start (Profiler via CDP):
- app-phone.js barFit (shared shell, 0.8 + LANG-35): ran on every un-hide while the bar's scripts started, each time taking classes off <html> (restyle of the whole page) and forcing a layout. Now skips when its inputs did not change and waits for the bar to go quiet (80 ms). 100+ ms to 10 ms.
- app-devices-ui.js (shared shell, 0.8 Track ID): drew the whole Input devices settings panel (every action list from the command palette) at page load, about 120 ms. Now drawn when Settings opens.
- BimCraft design-ui.js mountProgram: the first massing search ran at load, about 215 ms and a 295 ms long task. Now runs when the tab is first on screen or asked for.
- ModelCraft modelcraft.js drawSwatches: material textures drawn in 50 ms slices; now three per slice with a pause (no long tasks).
Result here: CadCraft busy 820 to about 530 ms and no long task; BimCraft's long task 295 to 57 ms.
Shared shell files are not pinned, so /use already has the two shell fixes. The frozen 0.8.1 and 0.8.2 app folders still carry the BimCraft and ModelCraft start-up work: a rolling patch of those two files is the owner's call (memory release-to-try). Not fixed: PartCraft and DetailCraft WebGL set-up (software renderer in these tests, to check on real GPUs), ModelCraft's WebGL probe (about 100 ms), the 250-file module graph itself.
Community comments
No comments yet
Add detail as we go: how you would use it, files or steps that show the problem, what other programs do. The team reads every comment.
Sign in or create a free account to add a comment.