Ok, i can’t ofcause not say what caused this, and as i have as routine to reboot quit often (often after major updates) i also can’t say whether past months updates has/had an “impact” as you describe.
It’s a fact that HA is “developing” quite fast, with “major” changes/enhancements, so i believe it’s still a good idea to Reboot (even after an “automatic” Core/Supervisor Restart ) , normally i check the “logs” first before deciding whether to perform an additional Reboot
With i.e my Windows systems, i always Reboot(ones again) even if windows already “Rebooted” do to an update, because after such updates alot “new” configurations/changes etc. is made(implemented), after the automatic/required reboot/restart.
And i prefer my system to “start-up” without alot of “strange” errors/warnings ( Often caused by the fact that some changes is not “configured/changed” before such “restart” ), so a total Reboot( after the Restart ) use to “clear” the logs, and pleases my worries/conserns
No issues rebooting. Just wanted to check if I may have some misconfiguration causing this. Looks like I am not alone. So should be ok. Just wanted to post results after today’s update to 2023.11.2. The spike at 2:30pm never came down to the usual utilisation around 2GB.
I think the last update helped me, specifically core 2023.11.2. Memory doesn’t go to 100% anymore, it seems to stay normal. This is my 1 week old log… I am on raspberry 4, 8gb ram with ssd
I started noticing memory-leaking behaviour after upgrading from 2023.10.3 to 2023.11.1 or 2023.11.2. Running on rpi3 with 1GB ram noticed regular crashes. Downgrading back to 2023.10.3 resolved the issue immediately.
Something I wanted to clarify for some time and now I have a bit of time to clarify. There is a difference with how HAOS and PVE report memory usage.
Under HAOS you only get the actual memory usage of the system excluding buffer and cache.
Under PVE you get the full amount of memory allocated including buffer and cache. Cache can be in RAM but can also be on disk and usually consumes a considerable portion of RAM allocated to the VM.
I will provide an example with 8G RAM.
PVE reports 4G of RAM used which is true, but it is not all consumed by HAOS.
This is what HAOS reports. So where is the rest of memory, 3G in our case, gone?
To find out use top under Terminal in HAOS. You get something like the below. Of 4G used, 7M is shared, 300M is buffer and 2.5G is cashed
So when you reboot the VM you have a clean and reduced size cache. If you see memory use going up in PVE in most instances you have to increase the memory allocated to the VM as it wants to expand its cache. For example if you have 2G allocated, increase to 4G. If you have 4G increase to 6G. Reported memory utilisation under PVE means, your installed add-ons and HACS integrations require more RAM to run at optimum.
Increased memory utilisation in most cases should not worry you, you just have to allocate more RAM to the VM if possible. If not possible, the system will expand its cache onto disk. In rare cases increasing memory utilisation over time, especially if exponential, could mean a process is possibly not managing memory well.
A lot of the above graphs are from ProxMox. I just started using it yesterday, after having lots of trouble with corruption using VirtualBox. Like others, I noticed that HA is taking up lots of memory, according to Proxmox.
Do you mean sensor memory usage for individual addons or system? Im using glances addon for monitoring, and glances integration for sensors. But with built in System monitor integration the sensor for memory usage its there too
I’ve noticed this exact same behavior. I have an automation to inform me if memory breaches a threshold. I’ve had it for a very long time and it has never triggered but in the past month or so it has triggered after updates. Like him noticing that after rebooting the memory normalizes. This is absolutely new behavior. I have no idea what causes it, it seems benign only because we can reboot to clear it but it is certainly concerning
From an HA system monitor perspective it seemed there is/was enough memory available (even when I ran with 6GB). However, from the top command I see now (with 8GB enabled!) about only 1.6 free.
The HA system monitor appears the exclude the buff/cache as being used, right?
The proxmox graph also shows that the system wants/needs a bit more memory as it now takes more now 8GB is available. (why did it not do that before and still left some to spare?). Any explanations?
Or will it simply allocate more cache if it’s available?
Secondly, 6GB of active usage sounds like a lot. I do have a large system but is this abnormal? What are the big memory consumers in HA?
You can not use the monitoring in Proxmox.
The VM will use memory for cache, which it can release quickly, should it be needed.
In Proxmox it will just be seen as used memory.
( Often caused by the fact that some changes is not “configured/changed” before such “restart” ), so a total Reboot( after the Restart ) use to “clear” the logs, and pleases my worries/conserns 
yeah that dont look right
