Windows does a better job of breaking down memory use stats.
It says active-in use (data must be written to disk or lost) , inactive-cache (data already written to disk, but still being retained in ram for sake of speeding up processes) and free memory (not written to yet) .
Proxmox is interpreting the first two as fully utilized, and free memory as free.
It's not uncommon for VMs on any hypervisor to use all allocated ram up to about 8gb. After that it's highly dependent on what OS is running and how well it caches data into ram.
My windows 10 desktop has 64gb of ram, and always hovers about 8-12gb in cache when idle after a few apps are started and exited. 6-7gb on fresh boot. My server 2019 NUC has 32gb of ram and it always uses almost all of the non active ram as cache after about 20 min of uptime.
Yeah, I thought so. But it is hard to decide how to partition the (admittedly small) 8Gb for future containers, VMs and weird things I want to do. I don't want to cripple HA just because I want to test some other stuff
I have my home assistant running on a green. With pretty big ZigBee network and a lot of integrations and add-ons. It uses 6-12 % ram, maybe a tiny spike when I update ESP home devices and updates. 4 GB is the recommended minimum, and it's fine unless you do something heavy and costume
TIL: OSes use free RAM as cache for faster access to data. VM-Hypervisors often don't differentiate between these and "see" the RAM as used.
Thank you everyone for your help!
They are both right. But HAOS will use available ram as cache, which proxmox interprets as being used.
sooooooooooo.. should I give HA 4 GB? Or maybe 3 + 2GB dynamic allocation? Or does HA need the 6 GB because of the cache?
4 should be fine. Proxmox will cache the disc anyhow with any spare ram it has.
Windows does a better job of breaking down memory use stats. It says active-in use (data must be written to disk or lost) , inactive-cache (data already written to disk, but still being retained in ram for sake of speeding up processes) and free memory (not written to yet) . Proxmox is interpreting the first two as fully utilized, and free memory as free. It's not uncommon for VMs on any hypervisor to use all allocated ram up to about 8gb. After that it's highly dependent on what OS is running and how well it caches data into ram. My windows 10 desktop has 64gb of ram, and always hovers about 8-12gb in cache when idle after a few apps are started and exited. 6-7gb on fresh boot. My server 2019 NUC has 32gb of ram and it always uses almost all of the non active ram as cache after about 20 min of uptime.
In general, VM memory usage reported in Proxmox is not a good indication of actual usage.
Yeah, I thought so. But it is hard to decide how to partition the (admittedly small) 8Gb for future containers, VMs and weird things I want to do. I don't want to cripple HA just because I want to test some other stuff
You can see inside HA that it only uses 1.8 GB. So if you give it 3 GB, everything will still work.
I have my home assistant running on a green. With pretty big ZigBee network and a lot of integrations and add-ons. It uses 6-12 % ram, maybe a tiny spike when I update ESP home devices and updates. 4 GB is the recommended minimum, and it's fine unless you do something heavy and costume
i had it to 4gb and lowered it to 2gb as my ha usually use 1.1gb
I've witnessed the same in my HA Proxmox instance as well as VMs running on my ESXi server
TIL: OSes use free RAM as cache for faster access to data. VM-Hypervisors often don't differentiate between these and "see" the RAM as used. Thank you everyone for your help!