CPU profiling basics in Node.js - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start CPU profiling using Node.js built-in profiler.

Node.js

const profiler = require('inspector');
profiler.[1]();

Drag options to blanks, or click blank then click option'

AbeginProfiling

BstartProfiling

CinitProfiling

DlaunchProfiling

Attempts:

3 left

💡 Hint

Common Mistakes

Using a method name that does not exist like 'beginProfiling'.

Trying to call 'launchProfiling' which is not part of the inspector API.

The startProfiling method starts the CPU profiler session in Node.js.

2fill in blank

medium

Complete the code to stop CPU profiling and save the profile data.

Node.js

const inspector = require('inspector');
const session = new inspector.Session();
session.connect();
session.post('Profiler.[1]', () => {
  session.disconnect();
});

Drag options to blanks, or click blank then click option'

Astop

Bpause

Cend

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pause' which only temporarily halts profiling.

Using 'end' which is not a valid command in this context.

The stop command stops the CPU profiler and returns the profile data.

3fill in blank

hard

Fix the error in the code to correctly enable CPU profiling in Node.js.

Node.js

const inspector = require('inspector');
const session = new inspector.Session();
session.connect();
session.post('Profiler.[1]');

Drag options to blanks, or click blank then click option'

AstartProfiling

Bbegin

Cactivate

Denable

Attempts:

3 left

💡 Hint

Common Mistakes

Calling 'startProfiling' without enabling the profiler first.

Using non-existent commands like 'begin' or 'activate'.

The enable command must be called before starting profiling to activate the profiler.

4fill in blank

hard

Fill both blanks to create a CPU profile and save it to a file named 'profile.cpuprofile'.

Node.js

const fs = require('fs');
const inspector = require('inspector');
const session = new inspector.Session();
session.connect();
session.post('Profiler.enable');
session.post('Profiler.start', () => {
  setTimeout(() => {
    session.post('Profiler.[1]', (err, [2]) => {
      if (!err) {
        fs.writeFileSync('profile.cpuprofile', JSON.stringify([2]));
      }
      session.disconnect();
    });
  }, 1000);
});

Drag options to blanks, or click blank then click option'

Astop

Bprofile

Cdata

Dresult

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong command names like 'end' instead of 'stop'.

Using incorrect variable names for the profile data.

The stop command stops profiling and returns the profile data object.

5fill in blank

hard

Fill all three blanks to start profiling, enable the profiler, and then stop profiling correctly.

Node.js

const inspector = require('inspector');
const session = new inspector.Session();
session.connect();
session.post('Profiler.[1]');
session.post('Profiler.[2]', () => {
  setTimeout(() => {
    session.post('Profiler.[3]', (err, profile) => {
      if (!err) {
        console.log('Profile collected');
      }
      session.disconnect();
    });
  }, 500);
});

Drag options to blanks, or click blank then click option'

Aenable

Bstart

Cstop

Dpause

Attempts:

3 left

💡 Hint

Common Mistakes

Skipping the enable step.

Using 'pause' instead of 'stop' to end profiling.

You must first enable the profiler, then start it, and finally stop it to collect the profile.

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