As shown, the 64bit apps uses around 30% more memory in IOS. So one can only wonder why Apple didnt add an extra GB. But again, thats what future products are for.
Anand iPad Air review is up.
I don't buy the 6-wide issue. At least there's close to 0 chance Cyclone decodes 6 instructions per cycle, that'd be crazy. I wonder if Anand did not see something like 100% clock boost with a 3-wide machine.
Is the "low" amount of RAM a reason not to buy it? I mean, I have never noticed any problems on my iPhone 5, but I reckon the 64-bit CPU will consume larger amounts of RAM.
However, maybe your needs are different, so have you considered simply buying it and testing it before the return period ends? I'm doing the same, except I'm contemplating whether I should switch to the Mini 2 instead.
It doesn't make any sense just like it doesn't make any sense that 16GB of NAND adds $100.The thing is, they were sold out yesterday, and they won't receive new shipment until at least 2-3 weeks. However, they said I could get the 20% off if I payed today(Saturday), but won't get the iPad until they do.
I don't believe my needs are that high, but when I purchase a premium product, I want it to be premium. That includes the RAM. I'm going to jailbreak, and some of those tweaks will definitely requires some good chunks of physical memory.
I just can't believe they didn't include 2GB of RAM when they run on 64-bit. I mean, the new Nexus 7 runs at 2GB if RAM at 32-bit and is a lot cheaper. It just doesn't make any sense...
As shown, the 64bit apps uses around 30% more memory in IOS. So one can only wonder why Apple didnt add an extra GB.
http://www.realworldtech.com/forum/?threadid=137844&curpostid=137999And please notice that PAE/LPAE really matters only past 4GB. Linux already uses "high memory" past the 1GB (or 2GB) mark, and it already slows things down, and you actually want to use 64-bit already much earlier than you need PAE/LPAE.
Read that again. You want 64-bit before you want LPAE. Seriously.
By the time you need LPAE, you're basically already screwed. You've gone from "some of the memory can't be accessed directly" to most of the memory being that way, and so your inode and filename caches are going to be severely limited, and that generates a whole slew of problems for the memory allocators, and slows down many other common operations (like read/write etc).
Yes, yes, in limited use scenarios it will all still "work fine" (say, running mainly virtual machines or very specific user loads). And the extra memory will generally be better than not having it. But it's absolutely the inferior technical solution.
Thread reminds me of 2003, A64 all over again.
"Who needs more than 4GB of ram pfft gtfo!"
Better to have and not need than need and not have. :thumbsup:
I feel old
Do you not remember the change from 16-bit processors to 32-bit processors ? If you don't, then don't worry, you are not old yet.
I remember going from 8 bit to 16 bit. Applied Engineering memory cards that used bank switching to get more than 64k of ram.