Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
This is the "Verge Test" that was suggested last week in this thread. Multi-tab browsing is something that is of great interest to me as I am a total tab slut. If there was a support group called Tab Addicts Anonymous, then I would be the chairperson.

iPad Air 16GB Wifi only, clean reboot each time, no background apps, no tabs:

Apple Safari (SunSpider 379.8ms) - 10 tabs before a tab had to reload

Google Chrome (Sunspider 1376ms) - 7 tabs before I noticed the monochrome reloading effect, however after this I closed the tabs one by one and it was still happening! It was only when I got back down to 3 tabs, could it switch between them without reloading! Seriously, on 4 tabs, chrome had to reload….. yikes

iCab Mobile with Lastpass extension (SunSpider 1364ms) - 16 tabs! Yes, after 15 tabs, iCab mobile (my favourite third party browser before this test) was still able to switch between all Verge tabs without any reloads whatsover. Very, very impressive seeming it also includes lots of nifty features and addons.

Opera Coast (SunSpider 1364ms) - One tab. Fail app for power users. If I want full-screen, I can do that in iCab mobile……

Essentially the takeaway from this is that Safari is much better than Chrome or any other browser using Webkit as it has the Nitro javascript engine, unless you are really in love with Chrome shared bookmarks and tabs.

Personally, I think I will use a combination of Safari and iCab, until I put more of my passwords in keychain. If I can keep my browsing to under 10 tabs, Safari is the better option.

I have another test for you - latimes.com

This horribly coded site loaded pretty fast on my laptop, but took 39 seconds on iCab mobile, and 55 seconds in Safari. I couldn't believe how long it too in Safari, the first time I tried it didn't even load after 90 seconds, then I got the 55 second result, and then I cleared the cache and tried Safari again, it took 1 min 22 sec for the words LA Times to actually show up, and 2 minutes for the popup telling me they have an iPad app to appear.

So even nitro javascript can't save you from bad code.

Interesting, but unfortunately real world usage involves switching to/from other apps, at which point Safari's ability to hold tabs goes through the floor. I generally only use a few apps, Safari/Mail/Downcast/Alien Blue, and switching between those then going back to Safari meant it could barely hold ONE tab in memory while I was actively using it. This was on the Air, which I've returned. My iPad 3 handled the same behaviour much better, albeit was a lot slower rendering pages and reloading apps when it had too.
 
iOS7 running with apple.com open in safari uses around 900Mb...

If that's true, how would the 512 MB of RAM on my 4S running iOS 7 manage to work?

I don't see how iOS 7 can manage to hog more resources than a desktop OS. Especially since it runs on devices with less RAM.
 
Posted this in the 1GB RAM thread too, but I'll say it here too. I'm fairly convinced that Safari has a bad memory leak. Over this week I've been trying to monitor exactly what's going on.

I have an iPad Air and an iPad 4 both running the exact same (restored the 4's backup to the Air). I restarted both and first opened only Safari. I was able to open 10 tabs (same sites) on each with no reloading. I then opened a series of my most memory intensive programs - iPhoto and edited a couple of photos, Evernote with a huge notes database, a couple of magazine apps with issue sizes greater than 250MB. Still no reloads in Safari.

However, within 24 hours, Safari was reloading every tab every time even if I force quit all my other programs and left only 4 tabs open.

24 hours later I was having the same experience and this time I instead quit Safari only. From 4 tabs that would reload every single time I was able to keep 7-8 open with only rare reloads. This echoes my long-term experience on the iPad 4.

I think they can fix most of this in software.
 
I would have thought they will be using the new memory compression technology from Mavericks in iOS 7 with 64-bit. That would make up the for the 64-bit overhead.

From what I can tell, they are using the memory compression from Mavericks in iOS 7.

And this whole thing about 30% more RAM usage is getting a little old. A well-respected music app developer said his apps use 4% or 5% more RAM in 64 bit mode.

My real world experience with the iPad Air shows this figure is much closer to the truth than what has been repeated ad nauseum around here for the past week.
 
...And this whole thing about 30% more RAM usage is getting a little old. A well-respected music app developer said his apps use 4% or 5% more RAM in 64 bit mode. ...

I know right? One off the cuff comment in an online review and some here take it as gospel.

With all due respect to Anandtech, my money is on the Apple design team. They think 1GB is enough, and so far my iPad experience is A+ :apple:
 
So - is this issue really a Safari thing when multiple tabs are open? Are people really having serious RAM issues? Ive only had mine for a few days and have done a lot of the usual stuff I do with it. My impression so far is that its a pretty snappy device and if I am having low-memory conditions I certainly dont see any side affects or warnings that something is amiss. What I dont know cant hurt me, right? Or, should I be concerned? I have another 12 days on my return privvys at Best Buy. Id hate to take it back because there *might* be a problem with memory although its fleeting and only occurs if you do X, Y, and then a tap dance afterwards.

I believe some of the reports and comments here but this issue looks like it might NOT effect a large user base. I dunno.
 
If that's true, how would the 512 MB of RAM on my 4S running iOS 7 manage to work?

I don't see how iOS 7 can manage to hog more resources than a desktop OS. Especially since it runs on devices with less RAM.

Because it uses 32bit code and iOS 7 on512Mb RAM differs. The amount of ram on the iPad Air is 990Mb, take 30% off of that for all 64bit processes, that gives you around 660Mb. That 660Mb is not free ram, the OS is still to be taken away from that number. That leaves around 300Mb free for free ram.

On you phone, you have 512Mb, take off the OS, you have around 150-200Mb free.

64Bit has a massive hit on RAM making ram usage on the iPad Air compatible to your 4S.
 
Because it uses 32bit code and iOS 7 on512Mb RAM differs. The amount of ram on the iPad Air is 990Mb, take 30% off of that for all 64bit processes, that gives you around 660Mb. That 660Mb is not free ram, the OS is still to be taken away from that number. That leaves around 300Mb free for free ram.

On you phone, you have 512Mb, take off the OS, you have around 150-200Mb free.

64Bit has a massive hit on RAM making ram usage on the iPad Air compatible to your 4S.
You aren't accounting for compression at all.
 
Because it uses 32bit code and iOS 7 on512Mb RAM differs. The amount of ram on the iPad Air is 990Mb, take 30% off of that for all 64bit processes, that gives you around 660Mb. That 660Mb is not free ram, the OS is still to be taken away from that number. That leaves around 300Mb free for free ram.

On you phone, you have 512Mb, take off the OS, you have around 150-200Mb free.

64Bit has a massive hit on RAM making ram usage on the iPad Air compatible to your 4S.

Can you point to another source for this other than the Anandtech review? I'm curious to read more.
 
I don't give a damn how much RAM there is, how many cores the CPU has and how many bsplines the graphics card can handle. that's something for specs-kiddies. I only care about usability and speed. how they do it does not matter to me.

There were/ are UNIX based OS that work absolutely perfect with 500MB RAM, the whole RAM discussion came to life with this damned MS Windows crap.
 
this whole thing about 30% more RAM usage is getting a little old. A well-respected music app developer said his apps use 4% or 5% more RAM in 64 bit mode.

I know right? One off the cuff comment in an online review and some here take it as gospel.

Anyone else remember all the hullabaloo around here about expected app size increases when the retina iPad came out and how 16Gb devices would be crippled/useless? :rolleyes:
 
From what I can tell, they are using the memory compression from Mavericks in iOS 7.

And this whole thing about 30% more RAM usage is getting a little old. A well-respected music app developer said his apps use 4% or 5% more RAM in 64 bit mode.

My real world experience with the iPad Air shows this figure is much closer to the truth than what has been repeated ad nauseum around here for the past week.

So having less usable memory in the air versus the 4 is A-OK with you. Great. I'll add you to the "accept whatever apple gives and be happy about it" group.
 
Hey guys,

I went to the apple store in Sydney and played around with the air a little.

I opened the same websites on both my ipad mini and the iPad air to see when both would start reloading tabs. It's pretty damn disappointing:
iPad mini: 11 or 10 tabs, not sure
iPad air: 6 tabs

I restarted both iPads prior to the test. This was one of the major annoyances for me on the mini and the iPad air seems to be FAR worse at this. I hope people who have already bought the air could post some information on RAM usage after restart and compare it to the iPad 4 and mini.
I'm - what's the analyst rhetoric for this, uuhm - a billion percent sure that iOS 8 or even an update to iOS 7 will fix this, as it was fixed on the Mac with Mavericks already.

It'd be sufficient if Safari would retain the data that you've entered in a form over reloads, as some people smarter than me probably made "The interface shall remember your input unless you deliberately dismiss it" an axiom of UI design in one way or another, because the auto-save feature in Lion does follow that principle.

If they didn't, then they should, though - because it would've prevented a major part of the annoyance caused by the reloading, and technically it's data loss.
 
Last edited:
Look for affects on 64but for Pc's.

Ummmm, no. Not only is comparing different architectures and OS irrelevant, I have yet to see a single mention of this so called "issue" beyond the Anandtech review. I'd hate to think that comment is the ONLY source for all this whining about lack of RAM and 64 bit apps? :confused: There's got to be some other source???
 
Ummmm, no. Not only is comparing different architectures and OS irrelevant, I have yet to see a single mention of this so called "issue" beyond the Anandtech review. I'd hate to think that comment is the ONLY source for all this whining about lack of RAM and 64 bit apps? :confused: There's got to be some other source???

Something is going on. My exact same routines I developed over the last year on my Ipad 4 are no longer as smooth as they were. Even in 3rd party browsers I'm seeing reloading of pages where that was virtually never an issue for me on the 4.
 
So having less usable memory in the air versus the 4 is A-OK with you. Great. I'll add you to the "accept whatever apple gives and be happy about it" group.

Thanks, and I'll add you to the "complain on the Internet without knowing the shot" group. ;)

...

Seriously though, it's not that I'm A-OK with every design choice Apple makes but the iPad Air is the best performing tablet computer ever made, so that's what I'm happy about. :D
 
Something is going on. My exact same routines I developed over the last year on my Ipad 4 are no longer as smooth as they were. Even in 3rd party browsers I'm seeing reloading of pages where that was virtually never an issue for me on the 4.

Were you running iOS 7 before? :confused:
 
Should I get a 16 GB Air or 32 GB rMini? I will primarily use it at home and it will be wifi only. I will also be using the home sharing feature on my MBP. I won't be playing any games.
 
From the day it was released on my ipad 4.

Ok, I'm confused.

Something is going on. My exact same routines I developed over the last year on my Ipad 4 are no longer as smooth as they were...

iOS 7 hasn't been out that long. To blame issues on lack of RAM instead of a glitchy iOS seems odd. But whatever. I still have to find a reliable source of information for this supposed "RAM crisis" due to 64 bit outside the Anandtech article. Can someone PLEASE point me in the right direction? :confused: I would hate to think all this 64 bit "RAM is not enough" concern is because of this one review?

Help me out here.
 
Ok, I'm confused.



iOS 7 hasn't been out that long. To blame issues on lack of RAM instead of a glitchy iOS seems odd. But whatever. I still have to find a reliable source of information for this supposed "RAM crisis" due to 64 bit outside the Anandtech article. Can someone PLEASE point me in the right direction? :confused: I would hate to think all this 64 bit "RAM is not enough" concern is because of this one review?

Help me out here.

Mike Ash also mentioned it here: http://www.mikeash.com/pyblog/friday-qa-2013-09-27-arm64-and-you.html

The increased pointer size comes with a substantial downside: otherwise-identical programs will use more memory, perhaps a lot more, when running on a 64-bit CPU. Pointers have to be stored in memory as well, and each pointer takes twice the amount of memory. Pointers are really common in most programs, so that can make a substantial difference. Increased memory usage can put more pressure on caches, causing reduced performance.

Mike's one of the most respected developers (even by Apple) when it comes to development and technical analysis.
 
the reason why its 1gb is because there will be a pro version with 2gb for you to open 20 tabs in safari.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.