![]() iPad Air 2 (iOS 11.4, 2GB memory): 1.3GB can be allocated. ![]() iPhone 5s (iOS 10, debug mode, 1GB memory): 600MB can be allocated. ![]() I wrote a test app that measures how much memory an app can allocate before it's killed. I know that using too much memory means that when my app goes into the background, iOS will terminate it quicker. If you're inclined to say that it depends on the OS version, you can assume we're talking about iOS 7. I'm referring to the total memory used by the process - heap, stack, static data, code, Core Animation backing stores, etc. Is there a difference between the above? Is each individual app limited to a fixed amount of memory in the interest of keeping a few apps in the background, or can the foreground app kick out ALL background apps from memory, and take the whole 1GB (or 512MB) to itself (and the OS, of course)?ĭoes it matter whether the device is an iPad or an iPhone? If I get my app working on an iPad with 512MB memory, does it mean that it will also work on an iPhone with 512MB memory, and vice-versa? I know that UIViews, and their Core Animation backing stores, will take more memory on the iPad because of the larger screen size, but other than that, is the memory situation the same between an iPhone and an iPad with the same memory? On a device with 1GB memory, how can can one app use? On a device with 512MB memory, how much can one app use? ![]() I understand that this does not have a precise answer, and I'm looking for a range, like: "Apps are killed when they use 300-350MB on a 512MB device. What's the situation nowadays? I could do go buy a bunch of iDevices and do a test myself, but I wanted to check: Has anyone done a test? ![]() For the original iPad, with 256MB RAM, I found that my app could use up to 100-140MB before it got killed. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |