Unless the author is using some very slim distribution or perhaps something more interesting, it’s a challenge to run an up to date HTTP server like Apache or nginx on 128MB alone, even though it shouldn’t.
https://www.debian.org/releases/bookworm/armel/ch03s04.en.ht...
128MB should be plenty. I used systems for years with much less. But in reality, Linux is much heavier these days.
On an old laptop running Windows XP (yes, with GUI, breaking my own rule there) I've also run a lot of services, iirc on 256MB RAM. XP needed about 70 I think, or 52 if I killed stuff like Explorer and unnecessary services, and the remainder was sufficient to run a uTorrent server, XAMPP (Apache, MySQL, Perl and PHP) stack, Filezilla FTP server, OpenArena game server, LogMeIn for management, some network traffic monitoring tool, and probably more things I'm forgetting. This ran probably until like 2014 and I'm pretty sure the site has been on the HN homepage with a blog post about IPv6. The only thing that I wanted to run but couldn't was a Minecraft server that a friend had requested. You can do a heck of a lot with a hundred megabytes of free RAM but not run most Javaware :)
https://www.debian.org/releases/bookworm/armel/ch03s04.en.ht...
128MB should be plenty. I used systems for years with much less. But in reality, Linux is much heavier these days.
Where does one even find a VPS with such small memory today?
How much memory do you think it actually takes to accept a TLS connection and copy files from disk to a socket?
https://wiki.debian.org/DebianEdu/Documentation/Bullseye/Req...
* Thin clients with only 256 MiB RAM and 400 MHz are possible, though more RAM and faster processors are recommended.
* For workstations, diskless workstations and standalone systems, 1500 MHz and 1024 MiB RAM are the absolute minimum requirements. For running modern webbrowsers and LibreOffice at least 2048 MiB RAM is recommended.
`Error: Problem parsing d="M 16.66% 50% L 83.33% 50%"`