sbc-bench

Well aside from the usual Wirth's law answer, the key is high abstraction on all levels, which brings bloat with it. Eventually that bloat will get optimized, as that chart interestingly shows iphone responsiveness being somewhat corelated with increasing years. Same with Windows, where there was a sizable abstraction jump with Vista, which then got slowly optimized over 7, 8 and 10. There's even abstraction in memory management now, with 64 bit virtual address mapping. I've recently stumbled upon these ARM benchmarks https://github.com/ThomasKaiser/sbc-bench/blob/master/Result... and was surprised that the Pi 4 runs 10-50% slower in 64 bit mode compared to 32 bit. I'd expect there was also a notable speed decrease when going from 8 to 16 and 32 bit systems, since there's twice as much address data to fetch and process.

I added some sorted table variants: https://github.com/ThomasKaiser/sbc-bench/blob/master/result...

Visidata has no trouble importing the table: vd 'https://github.com/ThomasKaiser/sbc-bench/blob/master/Results.md'

> 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/Result...