15M web servers on one VM – smoltcp, DPDK, AF_XDP
https://kapteko.com/15-million-webservers/It was like in the 2000s, blogs wanted to share informatin but also be funny, something similar to a talk in a event? Later they only focused on SEO, so they optimized every word and paragraph, removing jokes, etc. I remember noticing this with the Digital Ocean docs, that ranked 1 for every tutorial in how to install stuff on servers.
Anyway, good times! I miss them.
The title is underselling the story. I thought the webserver would've been some extremely beefy server, but no. It's 10GB of RAM. That's a basic M4 mac mini territory (and even that one is much more beefier than OP's server)
You can go much lower. The goal was set at "15 million web servers" which is dependent on the definition of "a web server" to include some implementation details. From the client perspective it actually means 15 million IP/port combinations that respond to HTTP - which you can do all in one go with an appropriate wildcard selector (such as with iptables transparent proxy)
Love the humour and simplicity!
Seeing 'web', together with its first few sections, made me initially think about http parsing/switching and almost made me stop reading.
I audibly exhaled from my nose, thank you.
In this case, the constraint is "one VM with 10GB of RAM and 1 CPU core", which would definitely be able to run a single web server fairly well, and probably could run tens of them fairly well, as well.
But, when we get up to hundreds of them simultaneously, thousands of them, tens of thousands of them, well, the associated resource constraint problems just seem to compound at every level...
But let's not let that stop us, let's "go for broke" -- and attempt 15 Million!
It's an excellent thought and engineering exercise...
Anyway, the article is a great read. Worth reading by anyone into optimization of computing resources, and definitely worth re-reading in the future.
Related:
The C10K Problem (1999):
I was thinking for the last couple of days to have 10M+ app connections on one laptop as an extreme cost optimization excercise. Great timing.
micro kernel: a bit like microservices; eth process talks to ip process, ip process talks to tcp process, tcp process talks to web server; multiple IPCs per packet/PDU, rather slow, single crashing process can still take out everything.
exo kernel: web server asks kernel to get packets matching some filter, kernel passes packets matching the filter to web server, web server uses a eth/ip/tcp library to process the packets;
This one sentence is such a profound layering violation that it changes your perspective on the possible ways to write programs.
Putting uncomfortable and sad motivational speak into funny speak! You are not logically supposed to feel good when you fail, but your brain's language parts make you feel good chemically! Great idea!