Why the Second Call to a JavaScript Constructor Is Slower: Inside V8’s Inline Caches
An in‑depth analysis of V8’s Inline Cache mechanism shows how hidden classes, map transitions, type‑feedback vectors, and the IC state machine cause the second invocation of a JavaScript constructor to be slower than the first, while the third becomes faster, explaining performance variations in property accesses.
