Response time optimization in Node.js - Step-by-Step Execution

Concept Flow - Response time optimization

Request Received

↓

Check Cache

↓

Return Cache

↓

Fetch Data / Compute

↓

Store in Cache

↓

Send Response

↓

End

This flow shows how a server can optimize response time by checking cache first, then processing only if needed.

Execution Sample

Node.js

import http from 'node:http';
const cache = new Map();
http.createServer((req, res) => {
  if (cache.has(req.url)) {
    res.end(cache.get(req.url));
  } else {
    const data = 'Response for ' + req.url;
    cache.set(req.url, data);
    res.end(data);
  }
}).listen(3000);

A simple Node.js server that caches responses to reduce processing time on repeated requests.

Execution Table

Step	Request URL	Cache Check	Cache Hit?	Action	Response Sent
1	/home	cache.has('/home')	No	Compute response, store in cache	Response for /home
2	/home	cache.has('/home')	Yes	Return cached response	Response for /home
3	/about	cache.has('/about')	No	Compute response, store in cache	Response for /about
4	/home	cache.has('/home')	Yes	Return cached response	Response for /home
5	/about	cache.has('/about')	Yes	Return cached response	Response for /about

💡 Server keeps running; each request checks cache and responds accordingly.

Variable Tracker

Variable	Start	After Step 1	After Step 3	After Step 5
cache	{}	{'/home': 'Response for /home'}	{'/home': 'Response for /home', '/about': 'Response for /about'}	{'/home': 'Response for /home', '/about': 'Response for /about'}

Key Moments - 2 Insights

Why does the server check the cache before processing the request?

Checking the cache first (see execution_table steps 2 and 4) avoids recomputing the response, saving time and resources.

What happens if the requested URL is not in the cache?

The server computes the response, stores it in the cache (steps 1 and 3), then sends it to the client.

Visual Quiz - 3 Questions

Look at the execution table, what is the response sent at step 3?

A Response for /about

B Response for /home

C No response sent

D Error message

💡 Hint

Check the 'Response Sent' column for step 3 in the execution_table.

At which step does the cache first contain the '/about' URL?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the variable_tracker for cache contents after each step.

If the cache was empty and the first request was '/contact', what would happen at step 1?

A Return cached response

B Compute response and store in cache

C Send error response

D Ignore the request

💡 Hint

Refer to the action taken when cache.has(req.url) is false in the execution_table.

Concept Snapshot

Response time optimization in Node.js:
- Use a cache (e.g., Map) to store responses.
- On request, check cache first.
- If cached, return immediately.
- If not, compute response, store it, then return.
- This reduces repeated processing and speeds up responses.

Full Transcript

This example shows how a Node.js server can optimize response time by using a cache. When a request comes in, the server first checks if the response is already stored in the cache. If yes, it returns the cached response immediately, saving time. If not, it computes the response, stores it in the cache for future requests, and then sends it. The execution table traces multiple requests showing cache hits and misses. The variable tracker shows how the cache grows with each new URL. Key moments clarify why checking the cache first is important and what happens when a URL is not cached. The quiz tests understanding of cache hits, cache updates, and response actions. This approach helps servers respond faster by avoiding repeated work.

Practice

1. Which of the following is a common technique to improve response time in a Node.js application?

easy

A. Writing all code synchronously to keep it simple

B. Using only synchronous file system calls

C. Increasing the number of console.log statements

D. Using asynchronous functions to avoid blocking the event loop

Solution

1. Step 1: Understand Node.js event loop behavior

   Node.js uses an event loop that runs best when tasks are asynchronous, avoiding blocking operations.

2. Step 2: Identify the impact of async functions

   Using asynchronous functions allows Node.js to handle other requests while waiting, improving response time.

3. Final Answer:

   Using asynchronous functions to avoid blocking the event loop -> Option D

4. Quick Check:

   Async = faster response [OK]

Hint: Async code keeps Node.js responsive and fast [OK]

Common Mistakes:

• Thinking synchronous code is faster
• Ignoring event loop blocking
• Believing console.log improves speed

2. Which syntax correctly uses caching middleware in an Express.js app to improve response time?

easy

A. app.use(cacheMiddleware);

B. app.cacheMiddleware();

C. cacheMiddleware(app);

D. app.cache.useMiddleware();

Solution

1. Step 1: Recall Express middleware usage

   Middleware is added using app.use(middlewareFunction) to apply it to requests.

2. Step 2: Match correct syntax

   Only app.use(cacheMiddleware); correctly applies the middleware function.

3. Final Answer:

   app.use(cacheMiddleware); -> Option A

4. Quick Check:

   Middleware added with app.use() [OK]

Hint: Use app.use() to add middleware in Express [OK]

Common Mistakes:

• Calling middleware as a method on app
• Passing app as argument to middleware
• Using incorrect method names

3. What will be the output response time behavior of this Node.js code snippet?

const express = require('express');
const app = express();

app.get('/data', async (req, res) => {
  const data = await fetchDataFromDb();
  res.send(data);
});

function fetchDataFromDb() {
  return new Promise(resolve => setTimeout(() => resolve('DB Data'), 2000));
}

app.listen(3000);

medium

A. Responds after 2 seconds with 'DB Data'

B. Responds immediately with 'DB Data'

C. Responds immediately with an empty response

D. Throws an error due to missing callback

Solution

1. Step 1: Analyze fetchDataFromDb function

   This function returns a promise that resolves after 2 seconds with 'DB Data'.

2. Step 2: Understand async/await in route handler

   The route waits for fetchDataFromDb to finish before sending response, causing 2 seconds delay.

3. Final Answer:

   Responds after 2 seconds with 'DB Data' -> Option A

4. Quick Check:

   Await delays response by 2 seconds [OK]

Hint: Await pauses response until promise resolves [OK]

Common Mistakes:

• Assuming immediate response despite await
• Confusing async with synchronous code
• Expecting error without callback in async

4. Identify the bug in this Node.js code that aims to optimize response time using caching:

const cache = {};
app.get('/user/:id', (req, res) => {
  if (cache[req.params.id]) {
    res.send(cache[req.params.id]);
    return;
  }
  const userData = getUserFromDb(req.params.id);
  cache[req.params.id] = userData;
  res.send(userData);
});

medium

A. Cache is cleared after every request

B. res.send is called twice causing error

C. getUserFromDb is asynchronous but used synchronously

D. Cache keys are not strings

Solution

1. Step 1: Check res.send calls in both branches

   If cache hit, res.send is called, but code continues and calls res.send again after fetching data.

2. Step 2: Understand Express response behavior

   Calling res.send twice causes an error because response is already sent.

3. Final Answer:

   res.send is called twice causing error -> Option B

4. Quick Check:

   Only one res.send per request allowed [OK]

Hint: Return after sending cached response to avoid double send [OK]

Common Mistakes:

• Ignoring multiple res.send calls
• Assuming synchronous DB call is fine
• Not returning after cache hit

5. You want to optimize response time by streaming a large file in Node.js instead of loading it fully into memory. Which code snippet correctly implements this using Express?

hard

A. app.get('/file', (req, res) => { const fs = require('fs'); res.sendFile(fs.readFileSync('large.txt')); });

B. app.get('/file', (req, res) => { const data = fs.readFileSync('large.txt'); res.send(data); });

C. app.get('/file', (req, res) => { const fs = require('fs'); const stream = fs.createReadStream('large.txt'); stream.pipe(res); });

D. app.get('/file', (req, res) => { const data = fs.readFile('large.txt', (err, data) => { res.send(data); }); });

Solution

1. Step 1: Understand streaming vs full read

   Streaming sends file data in chunks, reducing memory use and improving response time for large files.

2. Step 2: Identify correct streaming code

   Using fs.createReadStream and piping to res streams data efficiently; other options load full file or use callbacks.

3. Final Answer:

   app.get('/file', (req, res) => { const fs = require('fs'); const stream = fs.createReadStream('large.txt'); stream.pipe(res); }); -> Option C

4. Quick Check:

   Stream large files with createReadStream + pipe [OK]

Hint: Use createReadStream and pipe to stream files [OK]

Common Mistakes:

• Using readFileSync blocks event loop
• Using readFile loads entire file before response
• Assuming sendFile streams automatically