Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Write speed is what's relevant for proper memory mangament.

----------

I keep telling people that iOS devices are not made for multitasking, but they are not getting it, as can be seen in these dumb threads, where they scream for more ram.

Let me explain once again:
Yes, only one app runs upfront, but once RAM is used up, apps "on-hold" in the background are force quit. Once :apple: makes 2gb standard across the board, apps will be developed in a way that they use more RAM. Then the same thing happens: you switch -> reload. Then threads will come up where people will ask for even more RAM and the cycle begins again ...

----------

The 'memory management' (if you can even call it that) of iOS is geared towards running only one stable app at a time. It is very obviously not programmed for multitasking. If you want real multitasking, you need a proper ssd and a real OS. (Like on the surface tablets for example).

Since the beginning of computing increasing RAM has been the quick way to help with problems that are actually not really RAM related. The bottleneck on iOS devices is clearly software and storage related. :apple: knows this and that is why they will only very, very slowly increase RAM specs.

The iPhone 5 had the same amount of RAM as my 6+ and kept apps and tabs from reloading wayyyyy less readily. As the i5 is 32Bit and the 6+ is 64Bit, it's fairly obvious that RAM is the reason for this. 64Bit devices use more RAM.

Another obvious clue that these reloading issues are due to RAM is that the iPad Air 2 also reloads apps and browser tabs wayyyy less readily than the 6+. The reason? It has 2GB of RAM.

If you're waiting for Apple to 'fix' this issue with a software update, you'll be waiting until the end of time. Quite why you RAM apologists will stop at everything except actually increasing the paltry and pathetic 1GB is beyond me. More RAM is the answer, whether you think that's uncool or not.
 
The iPhone 5 had the same amount of RAM as my 6+ and kept apps and tabs from reloading wayyyyy less readily. As the i5 is 32Bit and the 6+ is 64Bit, it's fairly obvious that RAM is the reason for this. 64Bit devices use more RAM.

Another obvious clue that these reloading issues are due to RAM is that the iPad Air 2 also reloads apps and browser tabs wayyyy less readily than the 6+. The reason? It has 2GB of RAM.

If you're waiting for Apple to 'fix' this issue with a software update, you'll be waiting until the end of time. Quite why you RAM apologists will stop at everything except actually increasing the paltry and pathetic 1GB is beyond me. More RAM is the answer, whether you think that's uncool or not.
I was not talking about fixing anything with software updates. :confused:

Your post is not really related to my post that you quoted. You either quoted the wrong post or you didn't understand my post at all.

Fix it.
 
Let me explain once again:
Yes, only one app runs upfront, but once RAM is used up, apps "on-hold" in the background are force quit. Once :apple: makes 2gb standard across the board, apps will be developed in a way that they use more RAM. Then the same thing happens: you switch -> reload. Then threads will come up where people will ask for even more RAM and the cycle begins again ...

This is true for a subset of apps, not every application will try to fill all the memory available.
You are right when you say that adding RAM won't solve the multitask problem, but they did increase the RAM with iPad Air 2 and the whole user experience improved a lot.
 
I was not talking about fixing anything with software updates. :confused:

Your post is not really related to my post that you quoted. You either quoted the wrong post or you didn't understand my post at all.

Fix it.

How so? My post invalidates what you said.
 
Not to mention that writing isn't all that important on a phone; reading is what makes it feel fast.
If you want multitasking, you need proper memory management. With proper memory management you need fast write speeds. The iPhone storage write speeds are ridicolusly slow.

----------

How so? My post invalidates what you said.
No. Your post indicates that you didn't understand my post.
 
[/COLOR]No. Your post indicates that you didn't understand my post.

I totally understand your post but disagree with it.
You seem to be dismissing my post when in fact it explains why RAM is the problem. If you're happy to stay with 1GB in 2015 and beyond then good luck to you.
 
If you want multitasking, you need proper memory management. With proper memory management you need fast write speeds. The iPhone storage write speeds are ridicolusly slow.

Yes, while I agree with that, it doesn't matter in the slightest, since iOS doesn't swap RAM to disk. What happens when the system runs out of memory is that it first starts booting static files that, if needed, can be quickly pulled from storage again, while app states are preserved. If more memory is needed it starts to shut down apps, those unused the longest first. In this scenario, write speeds are irrelevant, which is why newer iPhones perform very well generally, despite having poor random write speeds. A spinning disk would most certainly not outperform the storage in an iPhone, like you stated in one of your earlier posts, because it has much higher latency, that you would certainly notice and get tired of pretty quickly.

But anyway, in order to keep more apps from getting kicked out of RAM, we need more RAM. Simple concept that is impeded by Apple's bean counting. They should have moved to 2GB with the 5S.
 
Yes, while I agree with that, it doesn't matter in the slightest, since iOS doesn't swap RAM to disk. What happens when the system runs out of memory is that it first starts booting static files that, if needed, can be quickly pulled from storage again, while app states are preserved. If more memory is needed it starts to shut down apps, those unused the longest first.
I know. This is what I explained earlier.

----------

A spinning disk would most certainly not outperform the storage in an iPhone, like you stated in one of your earlier posts, because it has much higher latency, that you would certainly notice and get tired of pretty quickly.
You're obviously right. My hdd comparison was stupid.

----------

But anyway, in order to keep more apps from getting kicked out of RAM, we need more RAM. Simple concept that is impeded by Apple's bean counting. They should have moved to 2GB with the 5S.
... and they would've sped up the spiral that leads to the demand for more and more ram as I explained earlier. In the process they would've made old iOS devices obsolete quicker. Partially thanks to :apple:s policy on RAM, my original iPad and iPad mini still run like a charm with 256mb and 512mb RAM in them.
 
There are still people in 2015 who think just because other phones have more megapixels that they're better than the iPhone camera? Guess that money Samsung spends on marketing isn't going to waste. Iphone 6/6 Plus camera destroys the S6.
 
There are still people in 2015 who think just because other phones have more megapixels that they're better than the iPhone camera? Guess that money Samsung spends on marketing isn't going to waste. Iphone 6/6 Plus camera destroys the S6.
That doesn't really have much to do with RAM though.
 
I agree that it needs more RAM, especially the 6 Plus. Just not with people claiming the camera is behind competitors because it's 8MP.
In that sense, yes, not everything is just about numbers, or one particular number basically.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.