It’s very strange. Identical installation, on two Rpi4.
One 32bit 2025.11.3 use 0,7gb, the last ones 64bit 2026.07.2 use 1,5 gb of ram.
With the acutal ram price …
Bye
Sandro
Nothing strange at all… You aren’t comparing apples to apples. You have apples and oranges (different builds) compare bit depth on the same build for a valid comparison.
Also yes on average the 64bit depth will generally use slightly more ram.
Considering only one of the bit depths are supported since December… It’s a moot point.
2 Likes
I know that is deprecated.
“When the wise man points at the moon, the fool looks at the finger.”
HA has the same functionality between 2025.11.3 and 2026.7.2.
The major changes is make simplest automations , setup etc.
Not the core.
What’s the way? is using more resources only for don’t use yaml?
I started to use HA 8 years ago, when was enoght a rpi2. Now we need more power.
For do more or less the same things. Just simplest.
Bye
Sandro
p.s
I’m a fan of venv
We also once lived in caves with torches…
1 Like
6 months = double of ram
Moore’s Law “atipical”…
6 months + 32 vs 64 bit
You could try to ask your money back from NC.
I do understand that with current RAM prices this is not pleasant and you don’t have to update.
It’s all over: devs trying to tackle this problem, box-movers using in-between steps for RAM sizes.
EDIT: Hassos has been referred to now by HAOS
We will fundamentally disagree on this point. and that is where most of your size comes from.
Enjoy your fandom 
Look, you seem to be in disagreement with the 32-bit decision and thus the post - that’s nice and, It wont change. The reason dev teams do things like this is they simply don’t have the people to support it.
If you have to support multiple branches, you don’t get that support for free - so
- either they diminish their ability to put out new fixes and features by spending effort on building and supporting a 32-bit branch… which modern processors increasingly don’t support (the diminished capacity comes from dilution of the manpower capability by properly testing both branches)
or WORSE,
- They skimp on the less supported branches and they eventually drift for weird reasons mostly because nobody’s really testing anything and when real issues arise take herculean efforts to unwind the bug nobody caught 10 builds ago because they’re glossing the testing of that branch - this is a happy fun time in devland trust me…
SO… as a business, they needed to decide -
To expend the effort to support the thing that’s rarely run or you don’t - they decided don’t. Sorry for the 32-bit users. It’s not personal it’s just math, we also don’t run 16-bit Windows today and nobody thunks the process for the same reason. I’m actually commending the dev team for it - gutsy and right call. ESPECIALLY right if your main product is basically FREE.
If they (HA dev team) keeps dragging along old, dead, code they risk what held back Microsoft for years in older versions of Windows. (Yay, Backcompat!)
HA team seems to get this point really well. To the contrary, I also feel they play a little fast and loose on the dev schedule for my taste but that’s a personal aversion to risk preference not a business decision. Dropping a bit depth / processor family. Totally is.
Also sorry about the price of RAM - but that’s not anything HA team can do anything about - blame SK, Samsung, Nvidia for that… One of those guys a smidge more than the others. 
4 Likes
“When the wise man points at the moon, the fool looks at the finger.”
What I’m showing isn’t only difference between 32 and 64 but with 2026.4.1 version vs 2026.7.2.
I know that venv installation is deprecated, tomorrow I’ll deploy a 64bit Hassos with 2025.12.x version.
Please don’t start discussion about venv deprecated but stay on ram use.
This is the ram use both 64 bit
This is latest
I’m under the impression that you are not able to look further then your finger…
4 Likes
Just use that version forever and no longer howl at the moon about it. It works, as you said…
3 Likes
64bit will use more ram, because some value types will be doubles in size, such as float, int, double and so on.
Besides that NathanCu said it quite well regarding 32bit systems, but he forgot to mention that this is not only an issue with HA, but with all systems in general and that means devs working on other pieces of code have and will drop 32bit too.
Since HA built on a large number of such small pieces of code from upstream developers, then 32bit HA been severely crippled for a long time and the HA devs had to make a decision about when the crippling was too much for a decent HA product.
For the moment there might be an issue with ram prices, but ram was also becoming an issue with 32bit systems, because they can not address more than 4Gb.
2 Likes
The top picture (the one with 2026.4.1) only has 1GB RAM allocated and seems to be using only half of that. I’ve never seen HA use anything less than 1GB, even on the simplest installs, so chances are it’s using Swap which you’re not considering when comparing both systems.
Finally good comments @NathanCu , @ShadowFist , @WallyR . 
My question isn’t linked directly on ram prices. And not 32 vs 64.
My question is linked about the more resource that HA (Hassio, Hassos, HAOS, etc) are requiring with every new version.
I discovered HA since 8 years ago, and one of the very appreciated feature is that the software runs on SBC, with low requirement.
Every new version add more function to “hide” yaml for move to very easly GUI configuration.
And this for what price?
@ShadowFist the screens are referring venv installations (I know that is deprecated but only on the support by the team not about the running software) . The venv is clean and only Home Assistant Core software. Just to empiric test to show the different use of ram on same 64bit installation.
Sandro
Yes, I know they’re venvs, but it looks like this time you’re the one who’s looking at my finger.
The point I was trying to make is that you aren’t comparing like with like. If you want to do an empiric test, give both installs the same amount of RAM (2-3GB should be enough for a clean install without any additional integrations).
That way the only real difference between both instances is the 32 vs 64 bit, nothing else.
Hi Sandro, you might not know that once there was a statement that we would not need more then 640kB, yes exactly: 640 kilobytes!
You are using HA for about 8 years so you have experienced the changes.
My statement about caves and torches was to make a point.
I don’t know about the fruit company but aside from Windows it’s also a thing with Linux that hardware requirements are changing.
There are still users running HA on RPi3 and since you are fond of venv, it is still perfectly possible to install an older core version with a version of Python from that era.
Nobody forces you to update, just like you can still use a Windows, Linux, Android or any other OS from back then.
The fact that NC has chosen to make the UI more user-friendly and add features is something you just have to live with (or step away): it’s FREE software and the creator has a vision about it.
Of course you can vent your frustration that things are not the way you would like them to go, the train is rolling.
As already being pointed out about the amount of RAM used: swap is a thing + you want your system to use the RAM that is available instead of it sitting there and doing nothing.
All this is called evolution and you might not agree with it which is OK too.
You actually can’t, unless you use old hardware too.
There sinply often are no drivers available for old OS versions on newer hardware.
1 Like
Wally, yes I meant on old hardware since they want to stay with ‘older’ SBC’s and a RPi4 is not that old but in the meantime, it’s already 7y since it was launched.