Performance monitoring basics in Express - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is performance monitoring in software applications?

Performance monitoring is the process of tracking how well an application runs, including speed, responsiveness, and resource use, to ensure it works smoothly.

beginner

Name two common metrics tracked in performance monitoring.

Two common metrics are response time (how fast the app replies) and CPU usage (how much processing power the app uses).

beginner

Why is monitoring response time important in an Express app?

Because it shows how quickly the server answers requests, helping find delays that can make users wait or leave.

intermediate

What tool can you use to monitor performance in an Express.js application?

You can use tools like New Relic, PM2, or built-in Node.js modules like 'perf_hooks' to monitor performance.

beginner

How does logging help in performance monitoring?

Logging records events and errors, helping you spot when and where performance problems happen.

Which metric shows how long it takes for a server to respond to a request?

A Response time

B CPU usage

C Memory allocation

D Disk space

Response time measures the delay between a request and the server's reply.

What is a common tool to monitor Node.js or Express app performance?

A Photoshop

B PM2

C Excel

D Slack

PM2 is a process manager that also provides performance monitoring for Node.js apps.

Why monitor CPU usage in an Express app?

A To track user clicks

B To measure internet speed

C To count database records

D To check how much processing power the app uses

CPU usage shows how much of the processor's power the app consumes.

What does logging NOT help with in performance monitoring?

A Increasing server speed automatically

B Tracking events

C Finding errors

D Spotting performance issues

Logging helps find problems but does not automatically improve speed.

Which Node.js module can help measure performance timings?

A path

B http

C perf_hooks

D fs

'perf_hooks' provides performance timing APIs in Node.js.

Explain why performance monitoring is important for an Express.js application.

Think about what happens if the app is slow or crashes.

List common metrics and tools used for performance monitoring in Express apps.

Consider what you measure and what helps you measure it.

Practice

1. What is the main purpose of performance monitoring in an Express app?

easy

A. To measure how fast the app responds to requests

B. To add new features to the app

C. To change the app's user interface

D. To store user data securely

Solution

1. Step 1: Understand performance monitoring

   Performance monitoring tracks how quickly the app handles requests.

2. Step 2: Identify the main goal

   The goal is to find slow parts and improve speed, not to add features or change UI.

3. Final Answer:

   To measure how fast the app responds to requests -> Option A

4. Quick Check:

   Performance monitoring = measure response speed [OK]

Hint: Performance monitoring = measuring app speed [OK]

Common Mistakes:

• Confusing performance monitoring with adding features
• Thinking it changes the user interface
• Assuming it stores user data

2. Which Express middleware code snippet correctly measures request duration?

easy

A. app.use((req, res, next) => { const start = Date.now(); res.on('finish', () => { console.log(Date.now() - start); }); next(); });

B. app.use((req, res, next) => { const start = Date.now(); next(); console.log(Date.now() - start); });

C. app.use((req, res) => { console.log('Request received'); });

D. app.use((req, res, next) => { console.log('Start'); next(); console.log('End'); });

Solution

1. Step 1: Check middleware timing logic

   app.use((req, res, next) => { const start = Date.now(); res.on('finish', () => { console.log(Date.now() - start); }); next(); }); starts timer, waits for response finish event, then logs duration correctly.

2. Step 2: Compare other options

   app.use((req, res, next) => { const start = Date.now(); next(); console.log(Date.now() - start); }); logs too early before response ends. Another option lacks next() call. The remaining option logs 'Start' and 'End' immediately, not duration.

3. Final Answer:

   app.use((req, res, next) => { const start = Date.now(); res.on('finish', () => { console.log(Date.now() - start); }); next(); }); -> Option A

4. Quick Check:

   Use 'res.on("finish")' to measure full request time [OK]

Hint: Use 'res.on("finish")' event to log after response ends [OK]

Common Mistakes:

• Logging time before response finishes
• Forgetting to call next() in middleware
• Not using response events to measure duration

3. Given this middleware, what will be logged when a request takes 150ms?

app.use((req, res, next) => {
  const start = Date.now();
  res.on('finish', () => {
    console.log(`Response time: ${Date.now() - start}ms`);
  });
  next();
});

medium

A. No output logged

B. Response time: 0ms

C. Response time: NaN

D. Response time: 150ms

Solution

1. Step 1: Understand timer start and finish

   The timer starts at request start and logs when response finishes, so it measures full duration.

2. Step 2: Calculate logged time

   If request takes 150ms, logged time is approximately 150ms.

3. Final Answer:

   Response time: 150ms -> Option D

4. Quick Check:

   Timer logs actual elapsed time on 'finish' event [OK]

Hint: Logs time difference on response finish event [OK]

Common Mistakes:

• Assuming log happens immediately (0ms)
• Confusing timer start and end
• Expecting no output without console.log

4. Why does this middleware fail to log correct response time?

app.use((req, res, next) => {
  const start = Date.now();
  console.log(Date.now() - start);
  next();
});

medium

A. It logs after response ends, so time is too long

B. It logs before response finishes, so time is near zero

C. It uses wrong event to measure time

D. It does not call next(), so request hangs

Solution

1. Step 1: Analyze when logging happens

   Logging happens immediately after start, before response finishes, so duration is near zero.

2. Step 2: Check middleware flow

   next() is called, so request continues; no wrong event used; logging is too early.

3. Final Answer:

   It logs before response finishes, so time is near zero -> Option B

4. Quick Check:

   Log after response finish for correct timing [OK]

Hint: Log after response finishes, not before [OK]

Common Mistakes:

• Logging too early before response ends
• Forgetting to call next() (not here though)
• Using wrong event to measure time

5. You want to log slow requests taking over 500ms in Express. Which code correctly implements this?

hard

A. app.use((req, res) => { if (Date.now() > 500) console.log('Slow request'); });

B. app.use((req, res, next) => { const start = Date.now(); if (Date.now() - start > 500) console.log('Slow request'); next(); });

C. app.use((req, res, next) => { const start = Date.now(); res.on('finish', () => { if (Date.now() - start > 500) console.log('Slow request'); }); next(); });

D. app.use((req, res, next) => { console.log('Slow request'); next(); });

Solution

1. Step 1: Understand timing and event usage

   app.use((req, res, next) => { const start = Date.now(); res.on('finish', () => { if (Date.now() - start > 500) console.log('Slow request'); }); next(); }); measures time from request start to response finish, then checks if duration > 500ms.

2. Step 2: Check other options

   Other options either check time immediately (always near zero), use wrong conditions like Date.now() > 500, or log unconditionally for all requests.

3. Final Answer:

   app.use((req, res, next) => { const start = Date.now(); res.on('finish', () => { if (Date.now() - start > 500) console.log('Slow request'); }); next(); }); -> Option C

4. Quick Check:

   Check duration on 'finish' event, then log if slow [OK]

Hint: Check time after response finishes, then log if slow [OK]

Common Mistakes:

• Checking time too early (before response ends)
• Logging all requests as slow
• Not using 'finish' event to measure full duration