References — bi-10 Compositor and GPU

Primary sources first. In-tree Chromium docs beat any external source, including these modules.

Primary

• cc/README.md — the Chromium compositor, in-tree
• How cc works — layer trees, tiles, activation, draw
• GPU synchronization
• Viz / display compositor

Source

• cc/trees/layer_tree_host.h — main-thread side
• cc/trees/layer_tree_host_impl.h — compositor-thread side; the commit/activate split lives here
• cc/tiles/ — tiling and raster priority
• cc/input/ — compositor-thread scrolling, and when it must hand back to main

Why this matters at the application layer

• web.dev — Stick to compositor-only properties
• MDN — will-change — and the layer-memory cost of overusing it
• Passive event listeners: DOM Standard. A single non-passive wheel listener hands scroll performance to your worst long task — see fe-01 (sibling project).

Related modules

• bi-09 — Paint — property trees are shared between paint and compositing
• bi-11 — Scheduling — BeginFrame and the frame pipeline
• fe-01 — Execution model (sibling project) — measured: a CSS transform animation kept running through a total main-thread freeze

When a claim here proves stale, record it in PROGRESS.md section 7.