Question about memory use on the iPad
First, I am extremely pleased with the Mobile 10 app on the iPad...many things have been added or upgraded that we've been asking for, for years.
With that, I have a question about use. If I save layouts (not sure the correct name) so that I can slide over to them rather than re-create them, will this bog down my iPad? How does it affect performance? If the effect is negative, about how many layouts/panels would be reasonable to leave vs closing them?
(My iPad only has 64Gb of memory.)
Eating a steady diet of government cheese, and living in a van down by the river.
Comments
-
If I save layouts (not sure the correct name) so that I can slide over to them rather than re-create them
I think you mean tabs... which sounds counterintuitive. If you are swiping between resources, that is "tabs." Are we now talking about the same thing? NOTE: You can only have ONE "layout" open at a time. If you have multiple somethings open at once, it would be tabs.My iPad only has 64Gb of memory.
No. Your iPad has 64GB of storage. My brand new iPad has 3GB of Ram (memory) and 64 GB of storage. The newest iPad pro (base model) has 128 GB storage and 8 GB of memory (Ram).How does it affect performance? If the effect is negative, about how many layouts/panels would be reasonable to leave vs closing them?
I don't know... but how many are you talking about?0 -
OK, tabs.
I have about four there now. An ESV, an ESV plus a GNT, a GNT plus an apparatus, and maybe a NET or NASB.
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
-
OK, tabs.
I don't think you got your answer. But added to JT, I have a bad habit of large layouts, even on the mobile. Many multi-panels, tabs, and then wildly linked irrespective of index. It all seems to work (ignoring the blank panels when the logic fails).
My impression is text doesn't bother the iPad. But even with image rich tabs, I've seen no hic-ups.
0
