👀 Views: 37 💬 Answers: 1 📅 Created: 2025-07-14

node.js websocket performance JavaScript

I'm trying to implement After trying multiple solutions online, I still can't figure this out. I'm currently implementing a real-time chat feature using Node.js with the `ws` library (version 8.5.0) for WebSocket connections. However, when I simulate high server load, clients frequently lose connection, and I receive the behavior `ECONNRESET` on the server side. I’ve tried increasing the `server.timeout` property and handling `close` and `behavior` events, but the scenario continues. Here’s the code snippet where I set up the WebSocket server: ```javascript const WebSocket = require('ws'); const server = new WebSocket.Server({ port: 8080 }); server.on('connection', (ws) => { console.log('Client connected'); ws.on('message', (message) => { console.log(`Received: ${message}`); // Broadcasting to all clients server.clients.forEach((client) => { if (client.readyState === WebSocket.OPEN) { client.send(message); } }); }); ws.on('close', () => { console.log('Client disconnected'); }); }); ``` To simulate load, I used a simple script with 100 concurrent WebSocket clients connecting to the server: ```javascript const WebSocket = require('ws'); const totalClients = 100; let connectedClients = 0; for (let i = 0; i < totalClients; i++) { const ws = new WebSocket('ws://localhost:8080'); ws.on('open', () => { connectedClients++; console.log(`Client ${i + 1} connected`); }); ws.on('close', () => { console.log(`Client ${i + 1} disconnected`); }); } ``` I also checked the server logs to see if there were any signs of resource exhaustion, but everything seems normal. Given that I’m running this on a local machine, I'm not hitting any obvious limits on memory or CPU usage. I would appreciate any insights on how to stabilize the connection under load or recommendations on additional configurations I may have overlooked. This issue appeared after updating to Javascript 3.9.