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.
11 Comments
warbond@lemmy.world · 8 pts · 29d
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
whats_a_lemmy@midwest.social · 9 pts · 29d
Out Of Memory, but you can choose to believe what you like
warbond@lemmy.world · 4 pts · 29d
Lol, that makes way more sense, thank you. Clearly hadn't had enough coffee this morning!
f3nyx@lemmy.ml · 4 pts · 28d
no no... you're onto something
litchralee@sh.itjust.works · 1 pts · 29d
Is there a link somewhere? Maybe my reader isn't showing the link?
TheIPW@lemmy.ml · 1 pts · 29d
https://unknownuniverse.uk/tools/proxmox-calculator/
My bad lol
litchralee@sh.itjust.works · 1 pts · 29d
Was AI used to generate part or all of this tool?
TheIPW@lemmy.ml · 1 pts · 29d
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.
digdilem@lemmy.ml · 1 pts · 29d
It is possible to run Proxmox without using ZFS.
KairuByte@lemmy.dbzer0.com · 2 pts · 28d
Absolutely
B0rax@feddit.org · 1 pts · 16d
But if you run it in a cluster you can replicate the volumes across nodes when ZFS is used.