Why streams are needed in Node.js - Performance Evidence

Performance: Why streams are needed

HIGH IMPACT

Streams affect how efficiently data is processed and transferred, impacting memory usage and responsiveness during I/O operations.

Reading a large file to send over a network

Node.js

const fs = require('fs');
const stream = fs.createReadStream('largefile.txt');
stream.on('data', chunk => sendDataOverNetwork(chunk));

Processes file in small chunks, reducing memory use and keeping event loop free for other tasks.

📈 Performance GainNon-blocking I/O, low memory footprint regardless of file size

Reading a large file to send over a network

Node.js

const fs = require('fs');
const data = fs.readFileSync('largefile.txt');
sendDataOverNetwork(data);

Reads entire file into memory before sending, causing high memory use and blocking the event loop.

📉 Performance CostBlocks event loop during read, high memory usage proportional to file size

Performance Comparison

Pattern	Memory Usage	Event Loop Blocking	Responsiveness	Verdict
Read entire file at once	High (proportional to file size)	Yes (blocks event loop)	Poor (delays other tasks)	[X] Bad
Read file using streams	Low (fixed small chunks)	No (non-blocking)	Good (keeps app responsive)	[OK] Good

Rendering Pipeline

Streams allow data to flow in manageable chunks through the Node.js event loop, avoiding blocking and enabling faster response times.

→I/O Processing

→Event Loop

→Memory Management

⚠️ BottleneckBlocking the event loop by loading large data all at once

Core Web Vital Affected

INP

Streams affect how efficiently data is processed and transferred, impacting memory usage and responsiveness during I/O operations.

Optimization Tips

1Always use streams for large data to avoid blocking the event loop.

2Avoid loading entire files into memory for better scalability.

3Process data incrementally to keep your app responsive.

Performance Quiz - 3 Questions

What is the main performance benefit of using streams in Node.js?

A They block the event loop to ensure data integrity.

B They increase CPU usage by processing data faster.

C They reduce memory usage by processing data in chunks.

D They load all data into memory before processing.

DevTools: Performance

How to check: Record a performance profile while running file read operations; look for long blocking tasks and memory spikes.

What to look for: Long tasks blocking the event loop and high memory usage indicate poor streaming usage.

Practice

1. Why are streams needed in Node.js when working with large files?

easy

A. To process data piece by piece without loading the entire file into memory

B. To make the file smaller in size automatically

C. To convert files into images

D. To encrypt the file contents

Solution

1. Step 1: Understand memory usage with large files

   Loading a large file fully into memory can cause high memory use or crashes.

2. Step 2: Role of streams in data processing

   Streams let you read or write data in small chunks, reducing memory needs.

3. Final Answer:

   To process data piece by piece without loading the entire file into memory -> Option A

4. Quick Check:

   Streams save memory by chunking data [OK]

Hint: Streams handle data in chunks, not all at once [OK]

Common Mistakes:

• Thinking streams reduce file size
• Confusing streams with encryption
• Assuming streams convert file types

2. Which of the following is the correct way to create a readable stream from a file in Node.js?

easy

A. const stream = fs.readFile('file.txt');

B. const stream = fs.createWriteStream('file.txt');

C. const stream = fs.createReadStream('file.txt');

D. const stream = fs.open('file.txt');

Solution

1. Step 1: Identify the method for readable streams

   Node.js uses fs.createReadStream() to read files as streams.

2. Step 2: Check other options

   fs.createWriteStream() is for writing, fs.readFile() reads whole file at once, fs.open() opens file descriptor.

3. Final Answer:

   const stream = fs.createReadStream('file.txt'); -> Option C

4. Quick Check:

   Read streams use createReadStream() [OK]

Hint: Read streams use createReadStream(), write streams use createWriteStream() [OK]

Common Mistakes:

• Using createWriteStream for reading
• Using readFile which reads whole file at once
• Confusing open() with stream creation

3. What will the following code output when reading a large file using streams?

const fs = require('fs');
const stream = fs.createReadStream('largefile.txt');
stream.on('data', chunk => {
  console.log(chunk.length);
});

medium

A. Multiple numbers showing sizes of each chunk read

B. The total size of the file in bytes printed once

C. An error message because chunk.length is invalid

D. Nothing, because streams do not emit data events

Solution

1. Step 1: Understand 'data' event on readable streams

   The 'data' event fires multiple times, each with a chunk of data.

2. Step 2: What does chunk.length represent?

   chunk.length gives the size of each chunk in bytes, so multiple numbers print.

3. Final Answer:

   Multiple numbers showing sizes of each chunk read -> Option A

4. Quick Check:

   'data' event outputs chunk sizes repeatedly [OK]

Hint: Streams emit 'data' events repeatedly with chunks [OK]

Common Mistakes:

• Expecting one total size output
• Thinking chunk.length is undefined
• Believing streams don't emit 'data'

4. Identify the error in this code snippet that tries to read a file using streams:

const fs = require('fs');
const stream = fs.createReadStream('file.txt');
stream.on('data', (chunk) => {
  console.log(chunk.toString);
});

medium

A. Not handling 'end' event to close the stream

B. Using createReadStream instead of createWriteStream

C. Using arrow function incorrectly

D. Missing parentheses after toString method call

Solution

1. Step 1: Check usage of toString method

   toString is a method and needs parentheses to execute: toString()

2. Step 2: Verify other parts of code

   createReadStream is correct for reading, arrow function syntax is valid, 'end' event is optional here.

3. Final Answer:

   Missing parentheses after toString method call -> Option D

4. Quick Check:

   Methods need () to run [OK]

Hint: Remember to call methods with () [OK]

Common Mistakes:

• Forgetting parentheses on methods
• Confusing read and write streams
• Thinking 'end' event is mandatory for reading

5. You want to process a huge log file line by line without loading it all into memory. Which approach best uses streams to achieve this efficiently?

hard

A. Use fs.readFile to load entire file then split by lines

B. Use fs.createReadStream and split data chunks manually by newline characters

C. Use fs.createWriteStream to write lines one by one

D. Use fs.open and read fixed-size buffers without streaming

Solution

1. Step 1: Understand memory constraints with large files

   Loading entire file with readFile uses too much memory for huge files.

2. Step 2: Using streams to process line by line

   createReadStream reads file in chunks; splitting chunks by newline lets you process lines without full load.

3. Step 3: Why other options are less efficient

   createWriteStream is for writing, not reading; fs.open with manual buffer reads is complex and less efficient.

4. Final Answer:

   Use fs.createReadStream and split data chunks manually by newline characters -> Option B

5. Quick Check:

   Streams + chunk splitting = memory efficient line processing [OK]

Hint: Stream chunks and split by newline for big file lines [OK]

Common Mistakes:

• Loading whole file with readFile
• Using write stream to read data
• Ignoring chunk boundaries when splitting lines