Checking file existence and stats in Node.js - Performance & Optimization

Performance: Checking file existence and stats

MEDIUM IMPACT

This concept affects the responsiveness and speed of file-related operations in a Node.js application, impacting how quickly the app can proceed after checking files.

Checking if a file exists and getting its stats before processing

Node.js

import { access, stat } from 'node:fs/promises';
async function checkFile() {
  try {
    await access('file.txt');
    const stats = await stat('file.txt');
    console.log(stats.size);
  } catch (err) {
    console.error(err);
  }
}
checkFile();

Using asynchronous promises avoids blocking the event loop, allowing other tasks to run concurrently.

📈 Performance GainNon-blocking file checks improve responsiveness and throughput under load.

Checking if a file exists and getting its stats before processing

Node.js

const fs = require('fs');
try {
  if (fs.existsSync('file.txt')) {
    const stats = fs.statSync('file.txt');
    console.log(stats.size);
  }
} catch (err) {
  console.error(err);
}

Using synchronous methods blocks the Node.js event loop, delaying all other operations until file checks complete.

📉 Performance CostBlocks event loop for duration of file system access, causing slow response and poor scalability.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous file check	N/A	N/A	N/A	[X] Bad
Asynchronous file check with promises	N/A	N/A	N/A	[OK] Good

Rendering Pipeline

File existence and stats checks run outside the browser rendering pipeline but affect server responsiveness and user experience by blocking or freeing the event loop.

→Event Loop

→I/O Operations

⚠️ BottleneckSynchronous file system calls block the event loop, delaying all other operations.

Optimization Tips

1Never use synchronous file system methods in production server code.

2Use asynchronous promise-based APIs to keep the event loop free.

3Handle file errors gracefully to avoid blocking retries.

Performance Quiz - 3 Questions

What is the main performance problem with using fs.existsSync in Node.js?

A It blocks the event loop, delaying other operations.

B It uses too much memory.

C It causes visual layout shifts in the browser.

D It increases network latency.

DevTools: Node.js Profiler or Chrome DevTools Performance panel

How to check: Run your Node.js app with profiling enabled, perform file checks, and record the event loop activity to see blocking calls.

What to look for: Look for long blocking tasks in the event loop timeline indicating synchronous file system calls.