• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Leopard real amount of RAM used by application
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Leopard real amount of RAM used by application


  • Subject: Leopard real amount of RAM used by application
  • From: Frank Reiff <email@hidden>
  • Date: Tue, 13 Nov 2007 18:19:20 +0100

Hi,

I've got an application that does some very heavy Core Data processing. By "heavy" I mean that the application does nothing but process things inside Core Data for up to an hour, not that this processing is particularly complex.

While this processing is going on the application is starting to use a lot of RAM. I've kept memory utilization down by:

* break the process down into stages
* using an auto-release pool for each stage
* committing frequently during a stage (every 5000 or 500 records processed depending on what is being done).


On Tiger I got the memory utilization down to around 128Mb during the entire 60 minute run.

Now with Leopard, during the early stages memory utilization goes up to 1GB and stays there during the entire processing.

The thing is I don't know whether this means there's a leak or whether it's a problem with the way I measure memory utilization.

I simply use the activity monitor and look at the "real memory" and the "virtual memory" columns. The utilization that I refer to is the "real memory" column.

This is no doubt simplistic and I don't really know how the memory allocation schemes of Mac OS X work, much less what has changed in Leopard..

Is this 1 Gb simply used because it's there and no other processes need? will it go down again if Leopard needs the RAM? is the program going to run out of memory and crash?

What makes this a bit of a drag is that each test takes ages to complete, so I want to avoid using instrumented code or a managed execution environment if it's going to mean that the code takes 10 times longer.. surely there's a better way?

Some details that might help make sense of all this:

Test Rig: PowerMac 3Ghz, 2GB RAM, Leopard 10.5.0
Code: 10.4 SDK compiled with XCode 3.0

Any help would be much appreciated.

Best regards,

Frank
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Prev by Date: Re: Cocoa-dev Digest, Vol 4, Issue 217
  • Next by Date: NSLocale and measurement systems
  • Previous by thread: Re: Cocoa-dev Digest, Vol 4, Issue 217
  • Next by thread: Re: Leopard real amount of RAM used by application
  • Index(es):
    • Date
    • Thread