zp-create-destroy-hot — create-destroy-in-loop

ClaimCopy Anchor Link

Allocator.create/destroy(Node) vs MemoryPool under Zig 0.17.0 -Ofast on this Linux machine shows a clear before/after wall-clock gap.

How measuredCopy Anchor Link

• Harness: packages/zperf/examples/bench/evidence_fill.zig (rule zp-create-destroy-hot cases)
• Build: zig build-exe -Ofast · optimize_mode=fast
• Timing: Io.Clock awake; warm=2; median of 9 rounds
• before: create_destroy_loop
• after: memory_pool
• ops=200000
• Raw: zp-create-destroy-hot.jsonl

Runtime (this evidence file)Copy Anchor Link

Lint mappingCopy Anchor Link

zperf-lint zp-create-destroy-hot / create-destroy-in-loop. Default severity in rules.zig is info; see evidence-policy for keep/escalate. Evidence exists and agrees directionally.

VerdictCopy Anchor Link

Agree ~10.7× for fixed-size Node churn.

LimitsCopy Anchor Link

Variable-size objects need other pools.