VPS backup size comparison -- Alpine binary only base vs *BSD-current with sources, self-compiled
Alpine base, binary only, no sources, apk upgraded to edge: 662.81 MB
OpenBSD-current, self-compiled, with sources: 23.92 GB
FreeBSD-current, self compiled. with sources: 48.53 GB
NetBSD-current, self-compiled, with sources (including pkgsrc): 84.65 GB
Sizes reported by vmcontrol.linveo.com panel Backup page. The panel doesn't say the type of backup or the method of compression. Nevertheless, the relative size comparison seemed interesting.
Maybe I might try self-compiling Alpine. Has anyone here done that?
Thanks to @linveo for kindly donating the VPS used for NetBSD-current. ![]()
Thanked by (1)cmeerw

Comments
Just for comparison: the NetBSD images i create (for @linveo - others would be free to use those as well) use a 512 MB filesystem (and include base etc kern-GENERIC man modules rescue)
Impossible to resist installing @cmeerw's NetBSD 11.0 RC4 image and making a backup just to see the size comparison with Alpine.
Want to guess the backup size result before you see it?
NetBSD 434.94 MB
Alpine 662.81 MB
Thanks @cmeerw!
Thanks @linveo! 
I'm guessing you are backing the entire vm? Could it be that whatever backup solution you are using cant read the BSD's filesystem so it reverts to a bit for bit backup strategy?
How big are the filesystems in each vm?
If you really want to build a tiny distribution, you should look at Damn Small Linux or Linux from Scratch. There are plenty of really tiny distributions you can build from source. Gentoo was one of the most common where people would bootstrap from a tiny image and build the world around that.
"It's a hard life- to be a stick insect." - Karl Pilkington