Problem
The symmetric comparison now wins its warmed execution rows overall, but the cold lifecycle remains the largest verified gap. Each cold sample includes OS-thread spawn, context creation, global/intrinsic installation, workload parse/compile/configuration, one exact invocation, context destruction, and join for both engines.
The 2026-07-13 quick matrix shows zig-js roughly 3x to 8x slower than JSC on most cold rows. This is real product cost and must not be removed from the benchmark boundary.
Work
- Profile one-lane cold context creation separately from parse/compile and first invocation.
- Cache or share immutable intrinsic metadata and shapes where realm semantics permit.
- Reduce allocator, global installation, parser, compiler, and teardown overhead.
- Preserve independent realm identity and creator-thread affinity.
- Keep the symmetric cold runner and exact source unchanged.
- Add focused startup counters or microbenchmarks only where they identify actionable cost.
Acceptance
- Every full cold row remains above the benchmark timing floor and checksum-valid.
- zig-js beats the matching JSC cold lifecycle at 1, 2, 4, and 8 lanes for all four comparison workloads.
- No warmed or shared regression.
- Full tests and the complete publication matrix pass.
- The dated report and README describe the cold boundary and resulting ratios.