Section 02 of 05
How V8, the event loop, and memory really behave
V8’s optimization pipeline, the event loop, memory, and the measurement methodology that keeps a performance claim from being folklore.
Most performance advice is repeated rather than measured, and the half of it that was once true has usually expired. These articles run the code, name the engine version, and quote the output. Where a number cannot be reproduced, the prose says so.
- Articles
- 3
- Latest
- Series
- 2
- №03
The V8 object modelObject Shapes Are a Tree, and the Tree Is Shared
A hidden class is a node in a transition tree V8 keeps for the whole isolate — which is why an unrelated function can decide how your object is stored.
- №02
Async machineryThe Event Loop You Think You Know
Microtasks, rendering opportunities and starvation — what the loop actually does between your callbacks, in the browser and in Node.
- №01
The V8 object modelHow V8 Decides to Optimize Your Function
Two functions that look identical can run at very different speeds. The difference is usually shapes, inline caches, and a deoptimization you never saw.
Browse
Other sections
- Language internals3 articles
- Ecosystem and production2 articles
- Frameworks2 articles
- Tooling and build2 articles