2 ms·
> Using a 64-bit kernel (arm_64bit=1) just takes away 50MB of RAM, the worst choice is to combine 64-bit kernel and 64-bit userland since everything relevant ge
by diimdeep 5y ago
> Using a 64-bit kernel (arm_64bit=1) just takes away 50MB of RAM, the worst choice is to combine 64-bit kernel and 64-bit userland since everything relevant get slower, same tasks require much more memory and the device will start to swap if low on memory or even kill processes due to out of memory.
> As a rule of thumb you need almost twice as much RAM with a 64-bit userland compared to 32-bit with the same programs/services running. [1]
[1]: https://github.com/ThomasKaiser/sbc-bench/blob/master/Results.md https://github.com/ThomasKaiser/sbc-bench/blob/master/Result...
- viraptor 5y agoThat's not supported by any data posted there. You'd have to have almost all of your memory filled will pointers to achieve 2x increase which just doesn't happen in reality. Looking at a large application like Firefox https://www.raymond.cc/blog/mozilla-firefox-64bit-build-performance-compared-to-32bit/ https://www.raymond.cc/blog/mozilla-firefox-64bit-build-perf... you get ~30% increase.
- yjftsjthsd-h 5y ago>> As a rule of thumb you need almost twice as much RAM with a 64-bit userland compared to 32-bit with the same programs/services running. That doesn't make sense; going 64-bit should only double the size of pointers, it shouldn't touch the size of code or data in memory.