Handling connection events in Express - Performance & Optimization

Performance: Handling connection events

MEDIUM IMPACT

This affects server responsiveness and resource usage during client connections.

Managing client connections in an Express server

Express

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

app.on('connection', (socket) => {
  setImmediate(() => {
    console.log('New connection');
  });
});

app.listen(3000);

Defers work asynchronously to avoid blocking the event loop, allowing faster handling of other events.

📈 Performance GainNon-blocking event loop improves INP and server responsiveness.

Managing client connections in an Express server

Express

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

app.on('connection', (socket) => {
  // Heavy synchronous processing
  for (let i = 0; i < 1e7; i++) {}
  console.log('New connection');
});

app.listen(3000);

Heavy synchronous work blocks the event loop, delaying handling of other connections and requests.

📉 Performance CostBlocks event loop causing delayed response and higher INP.

Performance Comparison

Pattern	Event Loop Blocking	Connection Handling Delay	Resource Usage	Verdict
Synchronous heavy processing in connection event	Blocks event loop	High delay	High CPU usage	[X] Bad
Asynchronous deferred processing in connection event	Non-blocking	Minimal delay	Efficient CPU usage	[OK] Good

Rendering Pipeline

Connection events in Express affect the Node.js event loop and server responsiveness rather than browser rendering directly.

→Event Loop

→Request Handling

⚠️ BottleneckBlocking synchronous code in connection event handlers

Core Web Vital Affected

INP

This affects server responsiveness and resource usage during client connections.

Optimization Tips

1Avoid heavy synchronous processing in connection event handlers.

2Use asynchronous or deferred callbacks to keep the event loop free.

3Monitor event loop blocking to maintain server responsiveness.

Performance Quiz - 3 Questions

What is the main performance risk when handling connection events with heavy synchronous code in Express?

A Increasing browser rendering time

B Blocking the Node.js event loop causing delayed handling of other requests

C Causing layout shifts in the client UI

D Increasing CSS selector complexity

DevTools: Node.js Profiler or Chrome DevTools (Node)

How to check: Run the server with profiling enabled, record CPU profile during connection events, and analyze event loop blocking.

What to look for: Look for long blocking tasks in the event loop timeline indicating synchronous blocking in connection handlers.