After coming close to running out of resources last week and having to re-purpose another device turning it into a 3rd Proxmox node, it got me thinking about how easily ZFS ARC cache and VM overhead sneak up on you.
So, I built a basic tool for rough guidance.
It calculates vCPU overcommit ratios and RAM allocation locally in your browser. Just pure client-side math so you don’t accidentally OOM your hypervisor like I almost did. Inputs stay right in your browser and aren’t saved anywhere.
Feedback or sanity checks on the math are welcome.
I’m new to this hobby and have only dipped my toes, but please tell me “out of mana” is a commonly accepted shorthand for this problem, because I love it
Out Of Memory, but you can choose to believe what you like
Lol, that makes way more sense, thank you. Clearly hadn’t had enough coffee this morning!
no no… you’re onto something
I’ve OOM my Proxmox numerous times, too expensive to upgrade, so far has corrupted my VM’s a small handful of times, shout out to
fsckfor bringing everything back in order.The worst is when the LVM-Thin storage is full, trying to get into a VM that can’t boot because it has no disk space left is horrendous and I never wish that upon anyone.
It is possible to run Proxmox without using ZFS.
Absolutely
Is there a link somewhere? Maybe my reader isn’t showing the link?
Was AI used to generate part or all of this tool?
I had the bulk of the tool written myself but used AI to help tweak the final polished version. I’ve always been open about my AI use in the past, I have a post on my blog about the subject. AI doesn’t generate my content, all ideas and opinions are my own but I do use it as a tool for refinement when needed.
