3 ms·
That was a remarkably poor article. Doubling your registers won't get you anywhere near to doubling your performance on real world code, especially when you al
by Symmetry 13y ago
That was a remarkably poor article. Doubling your registers won't get you anywhere near to doubling your performance on real world code, especially when you already have a decent number of registers like 16. Out of order chips like Apples that have caches they can hide the latency to in particular make this less of an issue. There are some integer loads that'll see something close to doubling performance from moving from 32 to 64 bit arithmetic, though.
Also, Android doesn't use Oracle's JVM. It uses Dalvik which Oracle doesn't control. And Linux already supports 64-bit operation and has for a long time. It's only recently supported 64-bit ARM, though, and Android will need to grab a more recent version of the Linux kernel if they want to use 64-bit ARM.
When Android supports 64-bit ARM they'll also benefit much more than Apple from the main advantage of 64-bit addressing when using less than 4 GB of memory: easier garbage collection. The larger your address space the less a random collection of bits will happen to constitute a valid pointer to a memory location.
- Steko 13y agoremarkably poor article. Doubling your registers won't get you anywhere near to doubling your performance on real world code Did you even read the article? "Double the register file adds a few percent to performance,” he said. “It’s a deep compiler and runtime VM issue. … So marginal improvements for most apps, at best."
- Zarathust 13y agoThe article has a lot of conflicting statements about this, which makes it rather poor. “This means that for some codes, the A7 will be twice as fast (or faster depending on how many memory accesses the original code had) to run code because the processor doesn’t have to use main memory as much.”