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.

Practice

1. What does io.on('connection', callback) do in an Express app using Socket.IO?

easy

A. Runs the callback when a user disconnects

B. Runs the callback when the server starts

C. Runs the callback when a new user connects to the server

D. Runs the callback when the server shuts down

Solution

1. Step 1: Understand the event name 'connection'

   The 'connection' event triggers when a new client connects to the server.

2. Step 2: Understand the role of the callback

   The callback runs code to handle the new connection, such as setting up listeners.

3. Final Answer:

   Runs the callback when a new user connects to the server -> Option C

4. Quick Check:

   io.on('connection') = new user connected [OK]

Hint: Remember 'connection' means user joined [OK]

Common Mistakes:

• Confusing 'connection' with 'disconnect'
• Thinking it runs on server start
• Assuming it runs on server shutdown

2. Which of the following is the correct syntax to listen for a user disconnect event on a socket?

easy

A. io.on('disconnect', () => { /* code */ })

B. socket.on('disconnect', () => { /* code */ })

C. socket.emit('disconnect', () => { /* code */ })

D. io.emit('disconnect', () => { /* code */ })

Solution

1. Step 1: Identify the object to listen on

   The disconnect event is listened on the individual socket, not the io server object.

2. Step 2: Use the correct method and event name

   Use socket.on('disconnect', callback) to run code when that socket disconnects.

3. Final Answer:

   socket.on('disconnect', () => { /* code */ }) -> Option B

4. Quick Check:

   socket.on('disconnect') = user left [OK]

Hint: Listen on socket, not io, for disconnect [OK]

Common Mistakes:

• Using io.on instead of socket.on for disconnect
• Using emit instead of on to listen
• Listening disconnect on wrong object

3. What will be logged when this code runs and a user connects then disconnects?

io.on('connection', (socket) => {
  console.log('User connected');
  socket.on('disconnect', () => {
    console.log('User disconnected');
  });
});

medium

A. User connectedUser disconnected

B. User disconnectedUser connected

C. User connected

D. User disconnected

Solution

1. Step 1: When user connects

   The 'connection' event triggers, logging 'User connected'.

2. Step 2: When user disconnects

   The socket's 'disconnect' event triggers, logging 'User disconnected'.

3. Final Answer:

   User connected
   User disconnected -> Option A

4. Quick Check:

   Connect then disconnect logs both messages [OK]

Hint: Connect logs first, disconnect logs second [OK]

Common Mistakes:

• Assuming disconnect logs before connect
• Missing that disconnect logs separately
• Thinking only one message logs

4. Identify the error in this code snippet that tries to log when a user disconnects:

io.on('connection', (socket) => {
  socket.on('disconnect', () => {
    console.log('User disconnected');
  });
});

socket.on('disconnect', () => {
  console.log('Another disconnect');
});

medium

A. The second socket.on('disconnect') is outside the connection handler and socket is undefined

B. The first socket.on('disconnect') should be io.on('disconnect')

C. The disconnect event should be 'disconnected' not 'disconnect'

D. The console.log statements are missing semicolons

Solution

1. Step 1: Check where socket is defined

   Socket is only defined inside the connection callback, so outside it socket is undefined.

2. Step 2: Identify the error

   The second socket.on('disconnect') is outside the connection handler, causing a runtime error.

3. Final Answer:

   The second socket.on('disconnect') is outside the connection handler and socket is undefined -> Option A

4. Quick Check:

   socket undefined outside connection callback causes error [OK]

Hint: Use socket only inside connection callback [OK]

Common Mistakes:

• Trying to use socket outside connection event
• Confusing event names 'disconnect' vs 'disconnected'
• Ignoring scope errors

5. You want to broadcast a message to all connected users except the one who just connected. Which code inside io.on('connection', (socket) => { ... }) correctly does this when a user connects?

hard

A. socket.on('message', 'A new user joined')

B. io.emit('message', 'A new user joined')

C. socket.emit('message', 'A new user joined')

D. socket.broadcast.emit('message', 'A new user joined')

Solution

1. Step 1: Understand broadcast

   socket.broadcast.emit sends to all except the current socket.

2. Step 2: Compare options

   io.emit sends to all including current socket; socket.emit sends only to current socket; socket.on listens, not sends.

3. Final Answer:

   socket.broadcast.emit('message', 'A new user joined') -> Option D

4. Quick Check:

   Broadcast excludes sender, perfect for this case [OK]

Hint: Use socket.broadcast.emit to exclude sender [OK]

Common Mistakes:

• Using io.emit which sends to sender too
• Using socket.emit which sends only to sender
• Confusing emit with on