Yes, I also agree. I just don't want to use any other browser, since I cannot change the default in iOS.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
All iPads iPad Air - how severe is the RAM problem?
- Thread starter vmflapem
- Start date
- Sort by reaction score
Yes, I also agree. I just don't want to use any other browser, since I cannot change the default in iOS.
Yes there are technical reasons for a substantial difference between 32 and 64 bit in ram usage. Anyone with the slighted computer knowledge knows that, its not something made up here. Even Apple have tutorials on how to conserve memory on the 32->64 bit transition.
https://developer.apple.com/library...e.html#//apple_ref/doc/uid/TP40013501-CH4-SW1
Because of improvements in 64-bit processors, 64-bit apps have the potential to perform faster than 32-bit apps. At the same time, the 64-bit runtime increases the size of pointers and some scalar data, resulting in a larger memory footprint for your app. A larger memory footprint results in increased pressure on processor caches and virtual memory and can adversely affect performance. When developing a 64-bit app, it is critical to profile and optimize your apps memory usage.
You are speaking about bytes and kilobytes in the worst case .... I say again, there is a difference for sure, but there is no SUBSTANTIAL difference. And there are very few 64-bit apps in the market right now ....
Yeah rightmove.co.uk. No haven't tried in other browsers because I'm stubborn. Shouldn't see why Apple's doesn't work perfectly well. There's other websites too, like asos.com, or websites with images.
OK, now I know the level to which I am dealing. I will stop talking about this, because nothing will come out of this aspect of our "debate".
Apple's A7 has the ability to allow 32 bit compatibility mode, so there is no need to emulate to run 32 bit code(unlike desktop/laptop).
Pointer size is bigger with 64 bit, that is a cold hard fact. Can one write an Obj-C program without pointers? Sure. Are there any apps in the app store that do not use pointers? No.
How many apps in the app store of compiled for 64-bit? I don't know, but the ones that are will be using more RAM, no matter how much you object.
You are not understanding, or refusing to acknowledge what I am saying. You point to apps running A-OK on the Air. That is immaterial if they are adhering to the RAM limit allowed by Apple. That has NOTHING to do with the amount if RAM, since it uses what it allowed to run. If anything, that should tell you that iOS can handle RAM just fine, since it manages the RAM usage between third party programs.
Great, so we are to accept unstable software from Apple?
http://www.smartdevicecentral.com/print_article/Mercury+Web+Browser+Pro+for+iPad/302699.aspx
Mercury is built upon webkit, so the "very few" of us experiencing tons of reloads are pretty much going to experience the same under other browsers using webkit.
No, but they can be a benchmark of the quality of one's code. Amazing how 7.1 is going to be the magic cure-all, but that simply means that apple has been working on iOS7 for well over a year, and they can't manage to produce a browser that doesn't crash on it's OWN SITE!!!!
Luckily I do not use facebook on iOS, but I know I can get safari to crash at least once a minute if I try scrolling a video embedded website the second it starts rendering. I am forced to sit there and wait before actually looking at the site, and even then, it crashes > 10% of the time. Would those blowups be mitigated with more RAM built into the Air? With the number of low memory warnings coming from Safari in my logs, I'd make an educated guess and say yes.
I went to the site and no issues tbh. I zoomed in and out on my Air. Scrolled down to find a property using the map. I zoomed in, chose London. I got the listing page zoomed in again and scrolled down to 7 bd detached house for rent 10,000 pds pw Upper Terrace, Hampstead London, NW3 BRP
Btw, holy crap, I thought living in San Francisco or NY was expensive. You guys have us beat by a mile.
Average 30% increase of what-ever the app currently is using, hardly insignificant.
The difference of running the same program on:
- JDK 1.5 32-bit
- JDK 1.5 64-bit
is 40% more memory use on the 64-bit JDK.
And that most program still only are 32-bit bit, is going to make it all much worse when they go 64-bit.
Pointer size is bigger, no one ever discuss about that.
But that doesn't mean you need to double the ram to have the system works flawlessly.
Very few ... What's your point ? They are requiring more ram, so ? How much more ? 100 Kb ? 10 Mb ?
I'm not understanding because you are speaking nonsense ....
No, and for this reason I switched to Mercury.
With mercury I'm experiencing almost no reloads at all.
Double the ram to solve a software issue is a very smart solution indeed ...
Luckily (for Apple) you don't work for Apple ...
There is NO reason why they couldn't have gone with at least 2gb. If only for tabbed web browsing. Apps may not demand much but websites are websites and it would be nice to have more than 3 tabs while working without crashing or reloading.
I like Mercury myself but I also had tabs reload as well. I found it no different than Safari when I open 5 tabs, open apps like Mail, iTunes Radio and move back in forth between them. When I go back and check on my tabs in Mercury, they begin to reload. It also happens to me in Safari.
I only did that as a test. Under normal instances I only use 1 tab in my web browser so the issue never comes up.
Or modify how the browsers work. I have an old Motorola Xoom which is Androids first tablet and has 1gb of RAM. I can have 20+ tabs open with music playing in the background and they won't reload without putting the browser in the background and running memory intensive apps in the foreground.
With my Air merely switching between tabs would reload them more frequently then I cared for.
So there has to be software alternatives to needing more RAM. How difficult that is to implement is another story.
There is a reason: $$$
I have a Lumia 925, an high end WP device from Nokia, and a 1320, a phablet, and they are working flawlessly with 1 Gb of ram.
Most of the Android smartphones on the market are still working with 1 Gb of ram (and Android is much less optimized than iOS or WP 8) ....
2 Gb will be welcomed in the next generation of iPhone and iPad, but in 2013 weren't necessary.
----------
I don't know about 5 tabs and a couple of apps, I don't really have a reason to keep 5 or more tabs opened on a tablet or a smartphone.
But I can surely work with 2-3 tabs and Mail without any refresh, using Mercury.
Now I'm testing iOS 7.1 and so far I didn't have any crash.
Neither do I but I was going to extremes because others have made comments about reloading with 5+ tabs open and 2 or more apps open then toggling back and forth between apps. I'm a light tablet user so I never run into any of those problems.
The reason isn't money. RAM isn't expensive and WP is a LOT lighter of an OS than iOS or Android. The reason is if Apple put more RAM in people would have less of a reason to upgrade to the next one.
Of course it's money. Apple has a certain price they want to sell at and any increases eat into their margins. Assume that an additional Gig cost them only one dollar. When you sell 20 million iPads, that's 20 million dollars of additional cost. For people that say Apple earns billions, 20 million dollars is still 20 million dollars. If the Apple engineers / software people tell management that it will run well with 1 Gig RAM, Apple isn't going to put 2 Gig in. If Apple thought they would have issues with 1 Gig, they would have put 2 Gig in.
Note - Don't assume they are going to 2 Gig this fall.
Well said that's why i'm not holding my breath we'll see a bump in memory with the Air 2. It would seem logical but if Apple can incorporate memory compression into iOS then there goes your 2GB.
I wish there were BTO systems, like Macs. I wish I could order an iPad with 4GB RAM for example..I know, I can keep dreaming.
I believe Apple's strategy is to hold back (i.e., under spec) at least one component/functional area each product release cycle to "encourage" the faithful to upgrade on a regular basis.
So they can get many of the people (especially those on this forum) to spend another $500-$1,000 on the Air2 so they can get better performance with 2GB ram.
BTW - 2GB ram will definitely improve performance, whether it's reduced tab refreshes in Safari, faster/smoother scrolling of web pages/Apple Store Icons, faster switching between apps, ability to run more graphic extensive games, etc. because the CPU can retrieve data faster from ram than SSD storage.
Since I upgraded to iOS 7, my iPad3 no longer scrolls smoothly in the Store and a number of apps. My guess is that Apple is swapping more data from ram to SSD to make more room in ram for iOS7; but the slower data retrieval from SSD is causing the scrolling to jitter.
It clearly demonstrates that a simple recompile from 32->64bit increases memory use drastically.
----------
It not, but its clearly demonstrates a simple recompile from 32->64bit increased memory consumption. Is that readly that hard to comprehend?
Not at the OS level but doesn't it load apps with their last state from flash as a method of multitasking? You could say that reloading Safari tabs is also a form of swap but from the website.