Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
No, Safari doesn't need (or use) 500 MB or anything close. That's why adding more RAM isn't going to fix the tab reloading problem:
It's not due to lack of RAM.

I don't know why people assume that it is, and cling to that idea against any argument. (Not saying you do, but there are some people that do. I think you're on the right track when you question if Safari could possible need 500 MB per tab... Of course the answer is no.)

If it is not a lack of RAM, then why does Safari always re-load its tabs? I can't think of another reason. It is incredibly annoying (especially when you are on slow internet). One time, I was filling out a form and needed to look something up. I went to Wikipedia, found what I needed to know, and when I went back to my previous tab, Safari had already clobbered it losing everything that I had typed.
 
The iPhone 6+ will be rending at 1242x2408 which is 4.11x the number of pixels of the iPhone 5S and hence will use 4.11x as much memory for compositing. In addition the iPhone 6+ then has to then down sample this render for the 1920x1080 screen, ultimately the memory used to display the screen also has to live in memory, resulting in an even higher use.

Andy, can you explain why the iPhone 6+ is doing things this way? I'm asking because I want to know, not because I doubt what you say or because I'm trying to argue with you.

Also, is it safe to say that this downsampling does not occur with an application that is written to support the native iphone 6+ resolution?

Thanks!
-Robert
 
Or just make it a couple of mm thicker and put a bigger battery, this way the lens doesn't stick out the back. Win-win.

I've said it on here before, but I absolutely would have traded some additional thickness for a flush camera and bigger battery. In a second.
 
They fixed that in iOS 8.

Are you serious that they fixed it? How well is it fixed (i.e. can you go back and forth between 4 or 5 tabs without reloading)?

If it is fixed, it will become my favorite iOS8 new "feature" :)
 
i don't think more RAM or any software fix would be able to "fix" the issue on safari reloading as you mentioned. think about it, RAM can be only given to number, let us say 6G. how many tabs can this 6G RAM hold? it has to have a limit. i am wondering whether you would complain it again after having 6G RAM?

on laptop or desktop, RAM size is more than that on iPhone. but still it has limited RAM size which eventually will hit a limit on how many safari tabs you can open.

to me, i opened many tabs as i can and DONT mind to reload those tabs.

for software fix, it might be ok to squeeze or zip the tabs data and still u have to reload it.

It's not about eliminating the issue completely. That is impossible without using paging (desktop OSs do it). It's about improving it by enough that it wouldn't matter. 2 gb of RAM would help a lot. You could keep 5+ tabs in memory, (including a few other apps) which would be enough even for the most "advanced iPad users". So please stop with that "Even with 55 gb of RAM it would reload with enough tabs open" nonsense.
 
Someone please tell me again why this RAM thingy is so important on the iPhone 6/6s. My HTC One with 2gb of RAM is constantly telling me that programs like Google+ are using too much and slowing down my system.

Any chance Apple has figured out a way to make apps and processes operate more efficiently with 1GB?
 
Now here's the thing. If it was display zoom, I don't think it would be such a low resolution. Plus someone overlayed the iPhone 6 Plus display over this image and it doesn't even size right. Even if it was display zoom, the screen shot would be the same size as a regular screen shot. It isn't.

I can also say I know someone who played with the phones at the keynote and told me the Plus will have 2GB of RAM and I'm confident in him because I know every thing about him, and he never lies. Doesn't make the rumor true or false.

1) Now here's the thing. If it was display zoom, I don't think it would be such a low resolution.
--> It's low-res because it's been resized..... God's sake......

2) Plus someone overlayed the iPhone 6 Plus display over this image and it doesn't even size right.
--> https://forums.macrumors.com/posts/19713797/ Get yourself updated.

3) I can also say I know someone who played with the phones at the keynote and told me the Plus will have 2GB of RAM and I'm confident in him because I know every thing about him, and he never lies.
--> Now, it's getting exciting!! So, he's invited to the show and got 6+ on his hands and could tell it has 2GB, right? But 'he never lies' doesn't mean 'he's correct', right?
 
do you know how much saving it will have by using 1GB ram instead of 2GB?
do you know how many risks it will introduce by including 1GB ram extra?
do you know how more efforts it will incur for engineer, manufacturer to get 2GB RAM?
do you know how much negative effect it will have by just using 1GB ram?
do you know whether it really matters with that extra 1GB ram to 99% of its users?

i do trust apple to make their own discretion to make their products. if i don't like their decision on design, then i just would not buy a damn thing from them.



What makes you think that the decision to put 1GB of RAM was made by 1000 engineers, and not by the bean counters trying to maximise profits knowing that people like you will buy whatever Apple makes so it doesn't matter what they put inside? Or by the people who are designing the iPhone 6s for next year and are trying to come up with its selling points (Look! iOS9 can multi-task! But you need to buy the new iPhone/iPad to take advantage of that, because it is *so* powerful...)
 
You guys don't get it, do you? Making the hideous, brick-like, "robert THICKE" iPhone 5s 0.7mm thinner was a wayyyyyy bigger priority than increasing its memory/capability/specs.
 
unbelievable for such an expensive phone with just 1GB RAM?

C'mon Apple don't be too greedy!!!
 
Andy, can you explain why the iPhone 6+ is doing things this way? I'm asking because I want to know, not because I doubt what you say or because I'm trying to argue with you.

Also, is it safe to say that this downsampling does not occur with an application that is written to support the native iphone 6+ resolution?

Thanks!
-Robert

One reason is that Apple wanted to keep the UI elements about the same size across devices.

John Gruber's write-up explains some of the rationale:

http://daringfireball.net/2014/08/larger_iphone_display_conjecture

Apple has always tried to avoid "scaling" since it does make things less sharp. However, I think that as screen density increases, that fuzziness gets less and less noticeable.
 
The great Tim Cook, at an Apple Event circa September 2015, was once quoted as saying:

"The response to the iPhone 6 and iPhone 6 plus has been absolutely overwhelming. Our customers are doing more than ever with their mobile devices and we at Apple are committed to their creativity..blah blah blah....double the RAM now."

Or maybe it was Eddie Cue, wearing a purple velour jumpsuit and slicked back hair who said "What's is gonna take for you to drive this thing off the lot today? Huh? How about I throw in an extra gig of ram for free and we call it a day? We gotta deal?"

I don't remember...
 
If it is not a lack of RAM, then why does Safari always re-load its tabs? I can't think of another reason. It is incredibly annoying (especially when you are on slow internet). One time, I was filling out a form and needed to look something up. I went to Wikipedia, found what I needed to know, and when I went back to my previous tab, Safari had already clobbered it losing everything that I had typed.

How is this related to the need for more RAM? I've seen this same behavior on my HTC One running Chrome and 2GB
 
If both iPhones are released with 1Gb of Ram, it will answer all of our questions. If the 6+ has app/safari reloads like the iPad air, then it needed more Ram. If the both run like dogs then they both needed more ram. Worst case would be if they run worse than an iPhone 5 or 5s

If they both offer more or less the same memory performance as the 5s then it might not be as big of a problem.

How well it run iOs 9 and 10 is another story altogether. Apple will have a fix for it though, buy the all new iPhone 6+OS or iPhone 7.
 
Pissed.

I truly hope that this is not the case.
I am quite the apple fanboy myself, but I simply cannot understand some ridiculous people who try to argue/defend Apple for including only 1gig of RAM while all other competitors are providing at least 2gig or more RAM on their top of the line devices.
 
so adding 1GB more only alleviate the issue, not the root cause and solve it?

what if someone wants to keep 10 tabs in memory?

It's not about eliminating the issue completely. That is impossible without using paging (desktop OSs do it). It's about improving it by enough that it wouldn't matter. 2 gb of RAM would help a lot. You could keep 5+ tabs in memory, (including a few other apps) which would be enough even for the most "advanced iPad users". So please stop with that "Even with 55 gb of RAM it would reload with enough tabs open" nonsense.
 
Someone please tell me again why this RAM thingy is so important on the iPhone 6/6s. My HTC One with 2gb of RAM is constantly telling me that programs like Google+ are using too much and slowing down my system.

Any chance Apple has figured out a way to make apps and processes operate more efficiently with 1GB?
You cannot really compare Android and iOS that way because their operating systems are implemented differently. Android was designed to run on as many different configurations of devices as possible, at the cost of (among others) additional resource utilization. This is the reason why you tend to see higher spec'd Android phones. Android's next generation runtime (the executor of programs) named ART is supposed to help bridge this gap. Read this if you're inclined to learn more about it. And here's a more detailed explanation of ART on Anandtech.
 
Last edited:
Any chance Apple has figured out a way to make apps and processes operate more efficiently with 1GB?

Apple can optimise iOS to use less memory, but the memory used by iOS is not the problem in the first place. For the apps that actually use all the memory and have the problem, the only thing that Apple can do is compress memory but then you have the CPU working overtime constantly and using up the battery.
 
Stop making excuses for Apple. Hardware and software are interdependent. If Apple is giving you just 1 Gig of ram, that means they're limited to writing software to only use 1 Gig of ram. Sure Apple can optimize for just 1 Gig, but then they'd have to leave out a lot ofneat functions and options. If you're in a bubble, that might be fine, otherwise the truth is you're missing out on a lot of new and exciting things. *Thats why Android users laugh at you when you get excited about something they've had for a while*
 
Last edited:
Someone please tell me again why this RAM thingy is so important on the iPhone 6/6s. My HTC One with 2gb of RAM is constantly telling me that programs like Google+ are using too much and slowing down my system.

Any chance Apple has figured out a way to make apps and processes operate more efficiently with 1GB?

It's not that important for many.

Safari re-loading can be solved without doubling physical RAM. 2GB will help, but it's not the only solution.

BTW, iOS and Android is two different things. iOS runs Apps straight but Android runs Apps in virtual machine, which compromises performance.

I'd like to say, iOS is a barbecue, and Android is Bain-marie (known as a double boiler).
 
Andy, can you explain why the iPhone 6+ is doing things this way? I'm asking because I want to know, not because I doubt what you say or because I'm trying to argue with you.

Also, is it safe to say that this downsampling does not occur with an application that is written to support the native iphone 6+ resolution?

Thanks!
-Robert

My best guess at the moment is it could be less taxing on the GPU the way Apple have decided to support this resolution. Basically they've decided to use @3x assets instead of @2.6x assets and instead of downsampling every image individually and trying to hold all the new samples in memory they seem to have just a single down sample at the end of the frame render and then dispose of it and start all over again.

There is a chance this final down sample is done in pure hardware as part of the final pass to the graphics display but somewhere ultimately this all has to live in memory.

Currently the research we've done on the simulator supports this theory as fonts at a certain point size should be rendered at a certain pixel size but they are actually rendered 0.87x their expected size.
 
Lol strokes 5S knowing i made the right decision not going for either the 6 or 6 Plus this year.:D

I feel come end of this week once benchmarks and reviews are out a few people that bought the 6 Plus thinking it was going to be better, are going to be really disappointed.

Looks like Apple saving all the goodies for the 6S and 6S plus, like open NFC and 2GB of ram & maybe a quad core A9.

Ah, yes, saying whatever makes you feel better about not getting the iPhone 6.

I had the iPhone 5 and I'm very excited for the iPhone 6+. I have Touch ID to look forward to, not to mention the A8 processor, large screen real estate, and to say the least iOS 8 with ApplePay. I look at what a phone has and what I PREVIOUSLY didn't. I really do hope you enjoy your 5s for another year, just don't stand too close to someone with a iPhone 6, trust me, it's gonna sting... just a little... :cool::apple:

Have a good day.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.