https://medium.com/@matteocroce/why-you-should-run-a-64-bit-...
Linux x32 ABI, the free 5-8% performance upgrade!
[1] https://www.youtube.com/watch?v=Mw-ravkg67k&
From René Rebe of T2-SDE pre-Gentoo source-based Linux distro fame.
I occassionally watch it, and the website is deceptive because the latest builds are much newer than the website suggests.
At 8 GiB RAM, allowing a single process to "only" use half of the available RAM really doesn't seem too limiting for most workflows. Especially considering that there's 4 CPU cores. If it's a notable hassle-free performance improvement it seems like a no-brainer for most use cases.
On ARM, there are patches implementing ILP32 with an A64 ISA (AArch64 mode and registers). While there probably is an improvement over the A32/T32 ISA, the benefit is not that great since the 32-bit ARM architecture already had 14 general purpose registers (AArch64 has 30).
The reason the arm64 ILP32 hasn't made it into mainline Linux is not fully justifying the software porting/maintenance cost over the benefit it brings. Full 64-bit software stack is in general a better option unless you run in a very constraint environment but, in that case, an M-class ARM CPU is probably a better option anyway.
Technically there’s a very interesting “hybrid” abi you can try - 32 bit pointers on a 64 bit ISA. The main benefit is the extra registers that get unlocked in 64-bit mode while keeping memory usage lower. It seems there’s an attempt to do this in Debian [1]. From what I read it’s not a big win for arm though but could be big for x86 - since the ISA is very different between x86 and x86_64. Probably doesn’t matter when ram is so cheap nowadays.
Separately I’ve now got a serious case of buyers remorse. I just bought the 4gb version last week. I would have easily shelled out an extra $20 for double the ram.
[1] https://wiki.debian.org/Arm64ilp32Port