fix: raise JS/TS noise floor to reduce false positive speedups#1820
fix: raise JS/TS noise floor to reduce false positive speedups#1820mohammedahmed18 wants to merge 1 commit intomainfrom
Conversation
…eedups Separate V8 processes have significant JIT/GC variance (15%+) that causes false positive speedups at the current 5% threshold. This raises the JS/TS noise floor to 15% (45% for <10μs functions) via a 3x multiplier. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Claude finished @mohammedahmed18's task in 2m 47s —— View job PR Review Summary
Prek ChecksAll ruff checks and formatting pass cleanly. No issues to fix.
Code ReviewThe PR is correct and well-structured. One minor issue found: Stale docstring in The docstring still says:
It should say 3x (this was the pre-existing value) and should now also mention the JS/TS multiplier. The Everything else looks good:
Duplicate DetectionNo duplicates detected. The Test CoverageAll 14 tests pass (11 existing + 3 new noise floor tests + 1 integration test).
|
Summary
compute_noise_floor()helper used by bothspeedup_critic()andget_acceptance_reason()Motivation
Analysis of 73 JS optimization PRs on a Strapi project revealed widespread false positives. Separate V8 processes have 15%+ JIT/GC variance between runs, but the acceptance threshold was only 5% — meaning process-level noise routinely exceeded the bar. For example, PR #40 claimed 10.6% speedup for a purely syntactic change (removing
{ return }braces), while functionally identical candidates showed a 16% swing.Test plan
🤖 Generated with Claude Code