:::note This post measures a renderer that has been deleted
The WeakMap<schema, record> measured below, the {type, attrs} schema objects it
was keyed by, and the ExoNodeDom renderer around them are gone
(packages/core/src/index.ts:10-12, packages/dom/src/index.ts:9-10). The
measurement stands as a measurement; the code it was taken on does not exist.
And the conclusion moved on three times. This post's fix was "put the record in a slot
on the schema object". After that the record became a TExoNodeDom that the CHILD owns
(packages/dom/src/dom/types/TExoNodeDom.ts), with the element pointing back under
Symbol.for('exo.child') — and on 2026-08-30 that back-pointer was removed outright, so an
element carries nothing at all. The "16% of an initial mount / 2.4–2.8× faster" figure that
used to be quoted for it is withdrawn: it was measured for a schema→record table, never
for an element-keyed one. What replaced it is the axis child-mark / pool, which prices
an element expando against a WeakMap entry directly.
It is kept because a post is a record of what was believed when it was written.
:::
A while back I wrote about why Exodra's WeakMap core beats the legacy one. Everything in that post is still true about design. This one is about what happened when I finally measured it: the renderer's WeakMap<schema, record> was costing about 11% of every mount, and moving the record onto a slot on the schema object got it back.