How many WebSocket connections can a $6 server hold? 99,770, and memory is the wall

DEV Community·6 points·remdore·10 days ago·dev.to

A plain Node WebSocket server on one shared vCPU held 99,770 live connections. Holding them cost 0-1% CPU; the real cost was 6.6KB of system memory each, half of it invisible to the process. The comfortable number is around 80,000.

Read the full article at dev.to →

#websocket #server #memory #connections #node #wall #many websocket #websocket connections

Related stories

Show HN: Zerikai Memory: local code-memory MCP server, now with Jevgithub.com
Hacker News · 1 points · about 13 hours ago
Show HN: Cross-platform governed memory for a fleet of agentsgithub.com
Hacker News · 1 points · 8 days ago
Show HN: I-server: Hide server using ICMP reflection/Destination Unreachablegithub.com
Hacker News · 4 points · 11 days ago
My Newsletter Server Is 1,258 Lines of node:sqlitedev.to
DEV Community · 3 points · 4 days ago
Show HN: Lossless-memory – a personal AI memory that never summarizesgithub.com
Hacker News · 67 points · 10 days ago
Show HN: Little Memory 2.0, one-line-a-day journal, offline-firstapps.apple.com
Hacker News · 1 points · 6 days ago

Related topics

memory101 highly10 node28 connections4 server92