Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Well explained. Thank you.
And your comment was well explained?

"As posted before:
https://en.wikipedia.org/wiki/Placebo"

And my claim was supported by multiple posts in this thread.
You've stated how Apple says their os works. Yes many people don't know how it works, for example some comments about battery life. But there hasn't been much talk about the facts on how it actually works.

Hey! You just stole that from Menneisyys2 without understanding it completely.
I actually wrote that before I even saw his post. But what he described is exactly what I've experienced. Oh, and well explained. Thank you.

You probably spend way more time closing apps and waiting for them to reopen unnecessarily than the app spends waiting for more RAM. :)
Maybe. But I do it when I choose to. I don't close all the apps unless it's being laggy. This might slow down opening up an app later, but I'm okay with that trade-off.

----------

It's not theory. It's how it technically works and is supposed to work. It's extremely efficient based on my findings. You can force the issue manually for problematic apps but if it's any, it's going to be one of three. Not all. Which is why it's not necessary.
Your response to the other post I quoted in that reply, from a developer explaining how it actually works and how it can be inefficient at times?
 
And your comment was well explained?

"As posted before:
https://en.wikipedia.org/wiki/Placebo"

I thought so. I was pointing out that your subjective experience could be colored by the placebo effect. Sorry if that was not clear enough!

You've stated how Apple says their os works. Yes many people don't know how it works, for example some comments about battery life. But there hasn't been much talk about the facts on how it actually works.

Well, other than the posts with actual processor usage. And the one that explained memory allocation.

I actually wrote that before I even saw his post. But what he described is exactly what I've experienced. Oh, and well explained. Thank you.

I was just kidding! :D

Maybe. But I do it when I choose to. I don't close all the apps unless it's being laggy.

How does that help? Sounds like cutting off your nose to spite your face. As pointed out in the post you agreed with, it just takes a few seconds for an app to request a full allocation of RAM. Closing all apps and then reloading would take even more time.

(With the obvious exception of misbehaving apps, as mentioned many times.)

This might slow down opening up an app later, but I'm okay with that trade-off.

Which was exactly the point that I've been making. It's a placebo. :) It makes you feel better!
 
I thought so. I was pointing out that your subjective experience could be colored by the placebo effect. Sorry if that was not clear enough!
And I was stating that my experience was not colored by the placebo effect.

Well, other than the posts with actual processor usage. And the one that explained memory allocation.
I don't think the cpu usage would affect what I'm talking about. You haven't really said much about Menneisyys2's post. He gives a technical description of pretty much exactly what I'm talking about.

I was just kidding! :D
hehe, oh okay! :D

Which was exactly the point that I've been making. It's a placebo. :) It makes you feel better!
What I was saying is that it helps me now (makes the current app work better), but hurts me later (gets rid of the benefit of storing other apps in ram).
 
I don't think the cpu usage would affect what I'm talking about. You haven't really said much about Menneisyys2's post. He gives a technical description of pretty much exactly what I'm talking about.

I'd just like to point out that what Menneisyys2 explains about isn't something that is going to effect every app. It's only specific to an app that needs to allocate a moderately large amount space that it knows it will need in order perform a time sensitive task in the near future. The problem that he stated was that their isn't a good way to communicate to iOS that an app will need memory, you can only communicate that you do need memory, and for a time sensitive task like his example that isn't good enough.

It was a valid point, and pointed out a real problem with iOS's memory management. I don't think that manually closing apps is really a very good solution to that problem though. It seams like that would be a band-aid at best, and could be solved in a much nicer way by Apple, by perhaps giving the programmer access to api to request space before it's needed, or by profiling apps to build a local database of how much ram is used on average for each app for the different tasks that the app performs. A nuke all apps button wouldn't be the best solution.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.