Matti

The biggest problem I have with my new vps: The #eleventy img based resizing (I think) means that a build of my blog maxes out the ram (12 GB, 6,99€ exc vat). Which I guess means I will have to upgrade to the next bigger machine (24 GB Ram, 13,99 exc vat).

P.S.: I am also dismayed how much ram is used for a machine outside of builds that does basically nothing, since nobody is visiting the vps based blog yet. And honestly even then… I guess #coolify is relatively heavy (and the idling db, redis, minio to power the dynamic bits of the blog probably don’t help)… makes me think that their “cloud option” is maybe not so bad a deal... I was initially skeptical, as the builds/deploys would still happen on my server, but if coolify uses (it seems) around 60% of my 12 GB ram all the time paying 5€ instead of upgrading my vps might be worth it instead). https://hachyderm.io/@finn_matti/115501969478983016

Nov 6 at 6:54pmWeb
Show threadFranticBiscuitNov 6

@finn_matti How are you calculating ram usage?

I'm also skeptical. What does free -m show in SSH?

Show threadMattiNov 6
@franticbiscuit “calculating” is a very generous term. Since I know what’s installed on the machine I just eyeballed it, tbh. I’ll take a look in a second.
Show threadFranticBiscuitNov 6

@finn_matti Yeah no worries, not trying to be like a prick or anything.

Sometimes those ram graphs calculate based on overall usage (including cached ram) which is not the same thing as free ram.

Show threadMattiNov 6
@franticbiscuit It’s a good point. I do notice that the blog is inaccessible during these peaks though. So those at least seem to be real. free -m now shows around 1.5 gb used. But I just upgraded/restarted the machine. Let’s see how things are going from here.