Spyke

Syndicated from the fediverse. Read and engage on the original instance.

View original on lemmy.ml

I built a basic Proxmox overhead calculator after nearly OOMing my cluster!

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.

https://unknownuniverse.uk/tools/proxmox-calculator/

https://unknownuniverse.uk/tools/proxmox-calculator/Open linkView original on lemmy.ml
13

11 replies

lemmy.world

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

8
warbondreply
lemmy.world

Lol, that makes way more sense, thank you. Clearly hadn't had enough coffee this morning!

4
lemmy.ml

It is possible to run Proxmox without using ZFS.

1

But if you run it in a cluster you can replicate the volumes across nodes when ZFS is used.

1

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.

1

You reached the end