CPU profiling basics in Node.js - Performance & Optimization

Performance: CPU profiling basics

MEDIUM IMPACT

CPU profiling helps identify how much processor time your Node.js code consumes, affecting responsiveness and throughput.

Identifying slow functions blocking the event loop

Node.js

import { Worker } from 'worker_threads';
const worker = new Worker(new URL('./heavyComputation.js', import.meta.url));
worker.on('message', () => console.log('Done'));

Offloads heavy work to a separate thread, keeping main event loop free.

📈 Performance GainReduces main thread blocking, improves INP significantly

Identifying slow functions blocking the event loop

Node.js

function heavyComputation() {
  for (let i = 0; i < 1e9; i++) {}
}
heavyComputation();

This blocks the event loop for a long time, causing poor responsiveness.

📉 Performance CostBlocks event loop for hundreds of milliseconds, increasing INP

Performance Comparison

Pattern	CPU Usage	Event Loop Blocking	Responsiveness Impact	Verdict
Synchronous heavy computation	High CPU	Blocks event loop for 100+ ms	High INP, poor responsiveness	[X] Bad
Offloading to worker threads	High CPU but parallel	No main thread blocking	Low INP, smooth responsiveness	[OK] Good

Rendering Pipeline

CPU profiling measures how JavaScript execution time affects the event loop and responsiveness in Node.js.

→JavaScript Execution

→Event Loop

→Callback Processing

⚠️ BottleneckLong-running synchronous JavaScript blocks the event loop

Core Web Vital Affected

INP

CPU profiling helps identify how much processor time your Node.js code consumes, affecting responsiveness and throughput.

Optimization Tips

1Profile CPU to find functions blocking the event loop.

2Avoid long synchronous JavaScript on the main thread.

3Use worker threads or async patterns to improve responsiveness.

Performance Quiz - 3 Questions

What does CPU profiling in Node.js primarily help you identify?

A Network latency issues

B Functions that block the event loop for too long

C Memory leaks

D CSS rendering delays

DevTools: Performance

How to check: Run Node.js with --inspect, open Chrome DevTools, record CPU profile during workload, analyze heavy functions.

What to look for: Look for long-running functions and event loop blocking time spikes.

Practice

1. What is the main purpose of CPU profiling in Node.js?

easy

A. To debug syntax errors in the code

B. To check the memory usage of the application

C. To monitor network requests

D. To find which parts of the code use the most CPU time

Solution

1. Step 1: Understand CPU profiling goal

   CPU profiling tracks where the CPU spends time during app execution.

2. Step 2: Compare options to profiling purpose

   Only To find which parts of the code use the most CPU time matches CPU time usage; others relate to memory, network, or syntax.

3. Final Answer:

   To find which parts of the code use the most CPU time -> Option D

4. Quick Check:

   CPU profiling = find CPU time hotspots [OK]

Hint: CPU profiling shows where CPU time is spent [OK]

Common Mistakes:

• Confusing CPU profiling with memory profiling
• Thinking it tracks network or syntax errors
• Assuming it shows all app performance issues

2. Which command correctly starts CPU profiling in Node.js?

easy

A. node --profile app.js

B. node --cpu-profile app.js

C. node --prof app.js

D. node --profile-cpu app.js

Solution

1. Step 1: Recall Node.js CPU profiling command

   The correct flag to start CPU profiling is --prof.

2. Step 2: Check each option's correctness

   Only node --prof app.js uses --prof, others are invalid flags.

3. Final Answer:

   node --prof app.js -> Option C

4. Quick Check:

   Use --prof to start CPU profiling [OK]

Hint: Use --prof flag to enable CPU profiling [OK]

Common Mistakes:

• Using incorrect flags like --profile or --cpu-profile
• Confusing profiling with debugging flags
• Omitting the --prof flag entirely

3. Given this command sequence:
node --prof app.js
Then running:
node --prof-process isolate-0x12345-v8.log
What is the output of --prof-process?

medium

A. The original JavaScript source code

B. A readable report showing CPU time spent in functions

C. A list of all files loaded by Node.js

D. An error message about missing files

Solution

1. Step 1: Understand purpose of --prof-process

   This command processes the raw CPU profile log into a readable report.

2. Step 2: Match output to options

   The output is a report showing CPU time spent per function, not source code or file lists.

3. Final Answer:

   A readable report showing CPU time spent in functions -> Option B

4. Quick Check:

   --prof-process = readable CPU time report [OK]

Hint: Use --prof-process to get readable CPU report [OK]

Common Mistakes:

• Expecting source code output from --prof-process
• Thinking it lists loaded files
• Confusing it with error output

4. You ran node --prof app.js but no log file was created. What is a likely cause?

medium

A. The app.js script exited too quickly before profiling started

B. You forgot to run node --prof-process first

C. You used --prof with an unsupported Node.js version

D. The log file is created only if you add --cpu-prof

Solution

1. Step 1: Understand profiling log creation

   The log file is created when the app runs with --prof and exits normally.

2. Step 2: Analyze why no log appears

   If the app exits too fast, profiling may not start or finish, so no log is saved.

3. Final Answer:

   The app.js script exited too quickly before profiling started -> Option A

4. Quick Check:

   App must run long enough to create profile log [OK]

Hint: App must run fully to generate profile log [OK]

Common Mistakes:

• Thinking --prof-process creates the log file
• Assuming --cpu-prof is required for logs
• Blaming Node.js version without checking

5. You want to find which function in your Node.js app uses the most CPU time. You run node --prof app.js and get a log file. What is the correct next step to analyze this data?

hard

A. Run node --prof-process on the log file to get a readable CPU profile report

B. Open the log file in a text editor and search for function names manually

C. Run node --inspect to debug the app instead

D. Restart the app without profiling to compare performance

Solution

1. Step 1: Understand how to analyze CPU profile logs

   The raw log file is not human-friendly; it needs processing.

2. Step 2: Use the correct tool for analysis

   Running node --prof-process on the log file converts it into a readable report showing CPU usage per function.

3. Final Answer:

   Run node --prof-process on the log file to get a readable CPU profile report -> Option A

4. Quick Check:

   Use --prof-process to analyze CPU profile logs [OK]

Hint: Process logs with --prof-process for readable CPU report [OK]

Common Mistakes:

• Trying to read raw logs manually
• Confusing profiling with debugging
• Restarting app without analyzing logs