brooklyn! 8142331616 bench(desktop): measure representative (warm-cache) cold start (#67733) ... Profiling the boot answered "is there a real cold-start win?": no wasteful hotspot — the renderer does only ~tens of ms of work at mount, no heavy library (shiki/mermaid/katex/d3/motion) initializes at startup; the rest is Electron runtime + waiting, near the Electron floor. It also exposed that the cold-start number was pessimistic: a fresh --user-data-dir per run means a COLD V8 code cache and worst-case bundle recompile every launch. Real users reuse their profile. Measured delta: fresh (cold cache): spawn→interactive ~1.48s reused (warm cache): ~1.0s So representative launch is ~1.0s; only first-launch-after-install pays ~+400ms. - coldStartSamples() reuses one profile (run 0 warms the cache, discarded; runs 1..N are warm samples), stepping ports + pausing so the single-instance lock releases. `--cold-fresh` measures the first-launch worst case. - Re-baselined cold-start with the representative warm numbers. Net: nothing high-ROI left to optimize. The only lever is shipping a pre-warmed V8 code cache to make first launch match warm (~400ms, once per update) — real packaging complexity for a marginal win, deliberately not pursued.		2026-07-19 23:21:45 +00:00
..
bootstrap-installer	fix(bootstrap): download timeouts + BOM upgrade for pre-fix cached scripts (#67193 follow-up)	2026-07-19 14:08:48 +05:30
desktop	bench(desktop): measure representative (warm-cache) cold start (#67733)	2026-07-19 23:21:45 +00:00
shared	fmt(js): npm run fix on merge (#66983)	2026-07-18 15:12:47 +00:00