Node.js Performance

Use this workflow to turn Node.js performance/resource investigations into safe, reviewable PRs.

Goals

• Improve execution time first: reduce p50/p95/p99 latency and increase throughput without changing intended behavior.
• Reduce CPU, memory, event-loop lag, I/O pressure, or lock contention when it supports execution-time gains.
• Ship small, isolated changes with measurable impact.

Operating Rules

• Work on one optimization per PR.
• Always choose the highest expected-impact task first.
• Confirm and respect intentional behaviors before changing them.
• Prefer low-risk changes in high-frequency paths.
• Prioritize request/job execution-path work over bootstrap/startup micro-optimizations unless startup is on the critical path at scale.
• Include evidence: targeted tests + before/after benchmark.