Node includes a built-in CPU profiler: `node --prof app.js` records samples, and `node --prof-process` turns them into a readable report showing where time is actually spent. `perf_hooks` lets you measure specific sections programmatically.
js
import { performance, PerformanceObserver } from "node:perf_hooks";
const obs = new PerformanceObserver((list) => {
for (const entry of list.getEntries()) console.log(entry.name, entry.duration.toFixed(2), "ms");
});
obs.observe({ entryTypes: ["measure"] });
performance.mark("start");
await heavyOperation();
performance.mark("end");
performance.measure("heavyOperation", "start", "end");Profile before optimizing: intuition about "the slow part" is frequently wrong, and optimizing the wrong section wastes effort while the real bottleneck (often a database query or an N+1 network call pattern) remains untouched.