Following up on my rant last month about the RAM crisis I decided to put my money where my mouth is. Or rather, my lack of money.

I set out to see if I could build a fully functional web stack on a Rock Pi S with only 512MB of RAM. No cheating. No massive swap files that kill the SD card. Just raw optimization and smart binary choices.

The Stack

• OS: Alpine Linux (the king of small). Using musl libc instead of glibc is a massive win. A standard “Hello World” in C with glibc is about 15-20KB; with musl, it’s half that. It adds up when you have dozens of processes.
• Server: Caddy (written in Go). I compiled it with CGO_ENABLED=0 to make it a static-pie binary.
• Database: SQLite. Stop using MySQL/Postgres for small personal projects. SQLite is just a file.
• App: A custom static blog and a small Go-based API for my notes.

The Secret Sauce: Stripping & Compressing

I didn’t just compile the apps; I stripped them. Running strip --strip-all on your binaries can remove megabytes of debug symbols you’ll never use. I also used UPX (Ultimate Packer for eXecutables) on some of the larger Go binaries to compress their on-disk size, though you have to be careful as this can sometimes increase RAM usage at runtime as it decompresses into memory.

The Results

When everything is up and running, the total RAM usage is… 82MB.

82 megabytes. I still have over 400MB free! I could run five more of these stacks on a single 512MB board. This proves that the “need” for 16GB or 32GB of RAM for a home server is mostly a lie sold to us by lazy developers who don’t want to optimize their garbage code.

How to Scale Small

1. Static is King: If you can generate it as HTML once, do it. Don’t make the server build the page every time someone visits. (This blog is 100% static, built with Hugo).
2. Beware of Python/Node: They are great for prototyping, but their runtime environments eat RAM for breakfast.
3. Turn Off What You Don’t Use: Check your running processes (btop is your friend). Do you really need avahi-daemon? Do you need bluetoothd on a headless server? Kill them.

Final Thoughts

Hardware prices might be rising, but our ability to optimize is unlimited. You don’t need a $2000 server to be part of the self-hosting revolution. You just need a bit of patience and a willingness to say “no” to bloat. It’s not just about saving money; it’s about the craftsmanship of code.

My 512MB challenge was a success. What’s the smallest specs you’ve ever run a “real” service on? Let me know.