Broadcasting to connected clients in Node.js - Performance & Optimization

Performance: Broadcasting to connected clients

MEDIUM IMPACT

This concept affects the responsiveness and scalability of real-time communication by how efficiently messages are sent to multiple clients.

Sending a message to all connected clients in a real-time Node.js server

Node.js

const messageBuffer = Buffer.from(message);
clients.forEach(client => {
  if (client.readyState === WebSocket.OPEN) {
    client.send(messageBuffer);
  }
});

Prepares message once as a buffer and sends it to all clients, reducing CPU overhead and memory allocations.

📈 Performance GainReduces CPU usage and memory pressure; lowers latency especially with many clients

Sending a message to all connected clients in a real-time Node.js server

Node.js

for (const client of clients) {
  if (client.readyState === WebSocket.OPEN) {
    client.send(message);
  }
}

Iterating over all clients and sending messages one by one can cause delays and block the event loop if many clients are connected.

📉 Performance CostBlocks event loop proportional to number of clients; increases latency linearly with client count

Performance Comparison

Pattern	CPU Usage	Event Loop Blocking	Memory Usage	Verdict
Sending messages one by one with string conversion	High	High (blocks event loop)	High (many string copies)	[X] Bad
Pre-buffering message and sending asynchronously	Low	Low (non-blocking)	Low (single buffer reuse)	[OK] Good

Rendering Pipeline

Broadcasting messages involves preparing data and sending it over network sockets, which impacts the event loop and network I/O stages.

→Event Loop

→Network I/O

⚠️ BottleneckEvent Loop blocking due to synchronous or repeated send calls

Core Web Vital Affected

INP

This concept affects the responsiveness and scalability of real-time communication by how efficiently messages are sent to multiple clients.

Optimization Tips

1Avoid synchronous loops sending messages one by one to clients.

2Pre-buffer messages to reuse the same data for all clients.

3Use asynchronous, non-blocking sends to keep the event loop free.

Performance Quiz - 3 Questions

What is a main performance problem when sending messages to many clients one by one synchronously?

A It reduces memory usage drastically

B It blocks the event loop causing delays for all clients

C It improves network throughput automatically

D It decreases CPU usage

DevTools: Performance

How to check: Record a performance profile during broadcasting; look for long tasks or event loop blocking times.

What to look for: Long blocking tasks or high CPU usage spikes indicate inefficient broadcasting.

Practice

1. What does broadcasting mean in the context of Node.js server with socket.io?

easy

A. Sending the same message to all connected clients at once

B. Sending a message to only one client

C. Receiving messages from clients

D. Disconnecting all clients simultaneously

Solution

1. Step 1: Understand broadcasting concept

   Broadcasting means sending one message to every connected client at the same time.

2. Step 2: Compare options

   Only Sending the same message to all connected clients at once describes sending the same message to all clients simultaneously, which matches broadcasting.

3. Final Answer:

   Sending the same message to all connected clients at once -> Option A

4. Quick Check:

   Broadcasting = send to all clients [OK]

Hint: Broadcasting means one message to all clients at once [OK]

Common Mistakes:

• Confusing broadcasting with sending to one client
• Thinking broadcasting disconnects clients
• Mixing up receiving and sending messages

2. Which of the following is the correct syntax to broadcast a message to all clients using socket.io in Node.js?

easy

A. io.send('message', data);

B. io.broadcast('message', data);

C. socket.emit('message', data);

D. io.emit('message', data);

Solution

1. Step 1: Identify broadcasting method in socket.io

   The method to send a message to all connected clients is io.emit.

2. Step 2: Check each option's correctness

   io.emit('message', data); uses io.emit, which is correct. io.broadcast('message', data); uses a non-existent broadcast method on io. socket.emit('message', data); sends only to one socket. io.send('message', data); uses send which is not the broadcasting method.

3. Final Answer:

   io.emit('message', data); -> Option D

4. Quick Check:

   Broadcast method = io.emit [OK]

Hint: Use io.emit to broadcast messages to all clients [OK]

Common Mistakes:

• Using socket.emit instead of io.emit
• Trying io.broadcast which does not exist
• Confusing send with emit

3. Given the following code snippet, what will be the output on all connected clients?

io.on('connection', (socket) => {
  io.emit('news', { hello: 'world' });
});

medium

A. Only the newly connected client receives { hello: 'world' }

B. All connected clients receive { hello: 'world' }

C. No clients receive any message

D. Only the server logs { hello: 'world' }

Solution

1. Step 1: Understand io.emit inside connection event

   Inside the connection event, io.emit sends the message to all clients, not just the new one.

2. Step 2: Determine who receives the message

   Since io.emit broadcasts, every connected client, including the new one, receives the message { hello: 'world' }.

3. Final Answer:

   All connected clients receive { hello: 'world' } -> Option B

4. Quick Check:

   io.emit sends to all clients [OK]

Hint: io.emit inside connection sends to all clients [OK]

Common Mistakes:

• Thinking only new client gets the message
• Assuming no message is sent
• Confusing io.emit with socket.emit

4. Identify the error in this code snippet intended to broadcast a message to all clients:

io.on('connection', (socket) => {
  socket.broadcast.emit('update', { status: 'new' });
});

medium

A. It will send the message to all clients except the sender

B. It will send the message only to the sender

C. It will send the message to all clients including the sender

D. It causes a syntax error

Solution

1. Step 1: Understand socket.broadcast.emit behavior

   The socket.broadcast.emit sends the message to all clients except the one that triggered the event.

2. Step 2: Analyze the code's effect

   Since the message is sent with socket.broadcast.emit, the sender does NOT receive the message, only others do.

3. Final Answer:

   It will send the message to all clients except the sender -> Option A

4. Quick Check:

   socket.broadcast.emit excludes sender [OK]

Hint: socket.broadcast.emit excludes sender client [OK]

Common Mistakes:

• Thinking broadcast sends to all including sender
• Confusing broadcast with io.emit
• Assuming syntax error

5. You want to broadcast a notification to all clients except the one who triggered an event. Which code snippet correctly achieves this?

hard

A. io.emit('notify', message);

B. socket.emit('notify', message);

C. socket.broadcast.emit('notify', message);

D. io.broadcast.emit('notify', message);

Solution

1. Step 1: Identify method to exclude sender

   To send to all except the sender, use socket.broadcast.emit.

2. Step 2: Check each option

   io.emit('notify', message); sends to all clients including sender. socket.emit('notify', message); sends only to sender. socket.broadcast.emit('notify', message); correctly sends to all except sender. io.broadcast.emit('notify', message); uses a non-existent method.

3. Final Answer:

   socket.broadcast.emit('notify', message); -> Option C

4. Quick Check:

   Exclude sender = socket.broadcast.emit [OK]

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

Common Mistakes:

• Using io.emit when sender exclusion needed
• Trying io.broadcast.emit which does not exist
• Using socket.emit which sends only to sender