CommonJS require and module.exports in Node.js - Performance & Optimization

Performance: CommonJS require and module.exports

MEDIUM IMPACT

This concept affects server-side module loading speed and initial script execution time in Node.js environments.

Loading modules in a Node.js application

Node.js

import fs from 'fs/promises';
async function readFile() {
  const data = await fs.readFile('file.txt');
  console.log(data.toString());
}
readFile();

Using ES modules with async file read avoids blocking, improving startup and responsiveness.

📈 Performance GainNon-blocking module loading and file reading, reducing startup delay and improving event loop availability.

Loading modules in a Node.js application

Node.js

const fs = require('fs');
const data = fs.readFileSync('file.txt');
console.log(data.toString());

Synchronous require and file read block the event loop, delaying startup and responsiveness.

📉 Performance CostBlocks event loop during require and file read, increasing startup time by tens of milliseconds depending on file size.

Performance Comparison

Pattern	Module Loading	Event Loop Blocking	Startup Delay	Verdict
CommonJS require with sync operations	Synchronous	Blocks event loop	High delay	[X] Bad
ES modules with async operations	Asynchronous	Non-blocking	Low delay	[OK] Good

Rendering Pipeline

In Node.js, CommonJS require synchronously loads and executes modules before continuing, blocking the event loop and delaying script execution.

→Module Loading

→Script Execution

→Event Loop

⚠️ BottleneckSynchronous module loading blocks the event loop, delaying all subsequent code execution.

Optimization Tips

1Avoid synchronous require calls during startup to prevent blocking the event loop.

2Prefer ES modules with asynchronous imports for better startup performance.

3Use Node.js profiling tools to detect blocking synchronous operations.

Performance Quiz - 3 Questions

What is the main performance drawback of using CommonJS require in Node.js?

A It blocks the event loop during module loading.

B It increases network latency for HTTP requests.

C It causes excessive memory usage.

D It slows down CSS rendering in browsers.

DevTools: Node.js --inspect with Chrome DevTools Performance panel

How to check: Run Node.js with --inspect flag, open Chrome DevTools, record performance during startup, and look for long blocking tasks.

What to look for: Look for long 'Script Evaluation' or 'Blocking' tasks indicating synchronous require or blocking operations.