Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
wow people get bent out of shape about the ram being used. As long as 20%ish of the ram is free you will not noticed any problem in perforce. Reason why is that 20% is plenty of room for the computer to move memory blocks around if they need to be reordered and provides plenty of room for a quick demand while it off loads other stuff to the flash memory.
Heck that could go easily as low as 10%. Now depending on the type of ram that is used chances are it has to be refreshed every 60micro seconds or it is lost any how.
 
wow people get bent out of shape about the ram being used. As long as 20%ish of the ram is free you will not noticed any problem in perforce. Reason why is that 20% is plenty of room for the computer to move memory blocks around if they need to be reordered and provides plenty of room for a quick demand while it off loads other stuff to the flash memory.
Heck that could go easily as low as 10%. Now depending on the type of ram that is used chances are it has to be refreshed every 60micro seconds or it is lost any how.

lol apparently people are very sensitive when it comes to their ram allocation.
 
wow people get bent out of shape about the ram being used. As long as 20%ish of the ram is free you will not noticed any problem in perforce. Reason why is that 20% is plenty of room for the computer to move memory blocks around if they need to be reordered and provides plenty of room for a quick demand while it off loads other stuff to the flash memory.
Heck that could go easily as low as 10%. Now depending on the type of ram that is used chances are it has to be refreshed every 60micro seconds or it is lost any how.

that's fine. now compress your computing space into 512mb with shared graphics and try to keep from hitting 10%.
ram is not an issue on my eight core mac pro with 10 gb...
 
that the taskbar is actually doing something? i'm pretty sure it needs memory to remember the app in a 'frozen' state.

... again, what are you getting at?

Memory containing cached data doesn't do anything to performance (other than improve it).

This older post on MacRumors provides Apple's explanation of this.

The RAM usage of an iOS App that isn't in the foreground will be in the "inactive" section.
 
Last edited:
So I will trust my experiences over some person spouting theory at me that it shouldn't lag my iphone. Plus, how do you know? Do you know each app I run? Do you know how well it uses multi tasking? Are you sure that each does it the most efficiently? Sure, you have your window of what apps use, that is a window of what apps you were running were using, not what I was running.

There's a difference between theory and fact.

iOS DOES NOT ALLOW MULTITASKING IN THE SAME WAY THAT MOST OPERATING SYSTEMS DO!

I don't know how that can be put more simply!

Your Apps cannot run in the background. There isn't a "more efficient" way to use multitasking. App A can't run in the background and neither can App B.

Apple provides no way for Apps to run in the background beyond 10 minutes.

It's not just that they say that they can't - the Developer has no way to write code that will execute in the background.

It's not possible!

Apple said:
Most applications that enter the background state are moved to the suspended state shortly thereafter. While in this state, the application does not execute any code and may be removed from memory at any time.

I can't fly to the moon - it's not because someone told me I can't, I just don't have a spacecraft to get me there.
 
Last edited:
There's a difference between theory and fact.

iOS DOES NOT ALLOW MULTITASKING IN THE SAME WAY THAT MOST OPERATING SYSTEMS DO!

I don't know how that can be put more simply!

Your Apps cannot run in the background. There isn't a "more efficient" way to use multitasking. App A can't run in the background and neither can App B.

Apple provides no way for Apps to run in the background beyond 10 minutes.

It's not just that they say that they can't - the Developer has no way to write code that will execute in the background.

It's not possible!



I can't fly to the moon - it's not because someone told me I can't, I just don't have a spacecraft to get me there.

Really? Pandora runs in the background playing music while you can do other things. So again you are wrong. :eek: :rolleyes:
 
Really? Pandora runs in the background playing music while you can do other things. So again you are wrong. :eek: :rolleyes:

Sigh. I don't know how many times you've called me wrong yet I've managed to reply with something that proves you are wrong. Have you even read the iOS API documentation?

Apps can do several limited things in the background:

- Playing Audio (as soon as this stops the App is terminated)
- Tracking Location (using the APIs that Apple provides)
- Maintaining a VOIP call (if no call is in progress, the App can only run once every 10+ minutes for a maximum of 30 seconds).

Nobody is talking about these scenarios. There clearly IS usage of the CPU and a real impact on memory usage with these things (as demonstrated by my use of Skype in the earlier screenshots).

Clearing Pandora from your Multitasking bar is going to massively hinder performance - your music will stop playing!
 
Last edited:
Sigh. I don't know how many times you've called me wrong yet I've managed to reply with something that proves you are wrong. Have you even read the iOS API documentation?

Apps can do several limited things in the background:

- Playing Audio (as soon as this stops the App is terminated)
- Tracking Location (using the APIs that Apple provides)
- Maintaining a VOIP call (if no call is in progress, the App can only run once every 10+ minutes for a maximum of 30 seconds).

Nobody is talking about these scenarios. There clearly IS usage of the CPU and a real impact on memory usage with these things (as demonstrated by my use of Skype in the earlier screenshots).

Clearing Pandora from your Multitasking bar is going to massively hinder performance - your music will stop playing!

You said APPs can't run in the background. So you were wrong. So don't say that next time. Lol


Sent from my AT&T iPhone 4 using Tapatalk
 
You said APPs can't run in the background. So you were wrong. So don't say that next time. Lol

Within the context of the discussion they don't.

I don't think we've spent three days discussing whether or not an App like Skype is running in the background when you're using it to make a call.

It doesn't use magic to work. Of course it runs in the background.

My earlier point still stands (and has not been refuted) - apps like Twitter don't run in the background.
 
Within the context of the discussion they don't.

I don't think we've spent three days discussing whether or not an App like Skype is running in the background when you're using it to make a call.

It doesn't use magic to work. Of course it runs in the background.

My earlier point still stands (and has not been refuted) - apps like Twitter don't run in the background.

Lo now you are trying to back out. I am done here with you. You said above no apps. You really have no clue.


Sent from my AT&T iPhone 4 using Tapatalk
 
Lo now you are trying to back out. I am done here with you. You said above no apps. You really have no clue.

You're backing out in a really cheap way here because you know that you're wrong.

IF you actually read what I posted, you'll find I didn't say "all apps"! I said "your apps" - I chose my words carefully.
 
You're backing out in a really cheap way here because you know that you're wrong.

IF you actually read what I posted, you'll find I didn't say "all apps"! I said "your apps" - I chose my words carefully.

Right..... Lol. Sorry but sure is funny that you really think you are right with no facts.


Sent from my AT&T iPhone 4 using Tapatalk
 
Right..... Lol. Sorry but sure is funny that you really think you are right with no facts.

Are you talking to yourself now?

I posted several pieces of evidence (i.e. facts) directly from Apple.com

You haven't posted a single piece of evidence to support your (incorrect) claims.
 
Last edited:
You need to ****. He said apps don't run in the background. He was wrong.


Sent from my AT&T iPhone 4 using Tapatalk

You really have no clue about how iOS and computer programs work do you?
Apps do not run in the background. Services do.
FFS educate yourself before posting more ignorant comments. You look like a fool.
 
What about those people who went over their data limit even when they were connected to wifi because apps were using 3G in the background? Anyone?

Those people must be using Windows Mobile 5. We are talking about the iOS4 here. ;)
 
You really have no clue about how iOS and computer programs work do you?
Apps do not run in the background. Services do.
FFS educate yourself before posting more ignorant comments. You look like a fool.

Umm you better research that again. LOL.
 
From APPLE...and it seems you guys are wrong again.

http://support.apple.com/kb/TS1295



Symptoms
Applications on iPhone or iPod touch may close unexpectedly because the device has begun to run low on application memory. This does not mean there is too much data stored on the device, but simply means that it is running too many memory-intensive tasks.

Some examples of this issue:

If you have many Safari web pages open on your iPhone or iPod touch, Safari may close and the iPhone or iPod touch will go back to the Home screen (where it shows all the application icons).
When listening to music or podcasts, watch video, etc. playback may stop and the device may return to the Home screen.
While using Safari or Maps and listening to music or podcasts, iPod audio playback may stop.
Applications purchased from the App Store quit immediately after you tap them.


Resolution
The following tips may help if this issue occurs and may help prevent these behaviors in the future.

Use iTunes to update to the latest version of the iPhone or iPod touch software.
Turn iPhone or iPod touch off and on and then reopen the application you were using. To turn the iPhone or iPod touch off and on, press and hold the Sleep/Wake button on top of device for a few seconds until a red slider appears, and then slide the slider. Then press and hold the Sleep/Wake button until the Apple logo appears.
With Safari, try to minimize the number of pages/browser windows that are open on the device by closing the Safari windows that are not being used.
On devices that support multitasking with iOS 4*, you can close applications running in the background. To do this, double-tap the Home button to display a menu of recent applications, then click the red minus on the icon for each application you wish to close.
If this issue occurs with applications purchased from the App Store, please see this document.
 
From APPLE...and it seems you guys are wrong again.

http://support.apple.com/kb/TS1295
On devices that support multitasking with iOS 4*, you can close applications running in the background. To do this, double-tap the Home button to display a menu of recent applications, then click the red minus on the icon for each application you wish to close.
*facepalm*

That's written for the average joe (apparently you). What they mean is applications running services in the background (Music, GPS, VOIP, uploading or downloading for x minutes). You can't argue how the iOS multitasking API's work as it's documented and plenty of devs use them! Apps that aren't doing anything in the background save their state and close. Upon reopening they quickly open from the saved state. It's a smart system that saves processing power and battery life.
 
*facepalm*

That's written for the average joe (apparently you). What they mean is applications running services in the background (Music, GPS, VOIP, uploading or downloading for x minutes). You can't argue how the iOS multitasking API's work as it's documented and plenty of devs use them! Apps that aren't doing anything in the background save their state and close. Upon reopening they quickly open from the saved state. It's a smart system that saves processing power and battery life.

http://www.youtube.com/watch?v=Su54MoeHUsg

Again.....seems me these guys and Apples document agree's with me. So you really think APPS in the background aren't using resources? LOL

Average joe? Seems to me that is what you folks are as I am more technically minded and know how it works with the facts. That is why you all own Macs.
 
Apps that have their states saved are only using the memory as a resource. No CPU cycles are being used in that case.

Per the developer forum, apps that are running in the background (Pandora) they are using CPU usage slightly. But memory is still being taken up either way if it's idle or being used like Pandora. Till that APP is closed, memory is being used to remember it's state which slows the phone down the more it fills up. It's all in the developer forums. Go read them, you guys might learn something.

This is my last post in this topic as I am done arguing with people who actually don't research things like this. I trust the developers themselves who know how APPs run on these phones and not end users.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.