15M web servers on one VM – smoltcp, DPDK, AF_XDP
- ID
- 48448
- Status
- summarized
- Published
- 19 Nov 2026, 1:56 PM
- Fetched
- 20 Nov 2026, 4:26 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://kapteko.com/15-million-webservers/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 6.0
- Created
- 20 Nov 2026, 4:27 AM
- Tags
- Audience
- developersvibe_coders
What happened
The author sets a deliberately absurd target: 15 million web servers on one VM with 10GB RAM and 1 CPU core, starting from a bare C listen/accept/recv/send/close loop that reaches about 65k RPS. When they try to launch 15 million instances, the run dies around 28,232 processes because port 0 draws from Linux's default ip_local_port_range of 32768–60999. The post uses that failure to explain why the default range is small and which ports are reserved.
Why it matters
If you plan to run many local listeners or containerized services, don't assume RAM or CPU is the first wall: the default ephemeral port range 32768–60999 stopped this run at roughly 28k processes. Allocate explicit ports or consolidate behind fewer listeners before scaling process count.
Discussion angle
The failure at ~28k processes is a good prompt: what would you change first—explicit port allocation, fewer processes with a shared listener, or a different networking stack like the smoltcp/DPDK/AF_XDP approaches named in the title?