• 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
Re: find out maximum number of objects in memory at once?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: find out maximum number of objects in memory at once?


  • Subject: Re: find out maximum number of objects in memory at once?
  • From: Tim MacDonald <email@hidden>
  • Date: Mon, 22 Dec 2003 00:53:41 -0800

Ben,

what are the limits for the number of objects in memory at one time (the smallest possible - 16 bytes each)? what does it depend on? is it just the amount of memory available or are there other limits which come into effect?

I've never had to worry about the maximum number of objects in any system. Is that right, 22+ million objects?
i just made a quick test and got to 22300000 objects but by that time some serious disk thrashing was going on - made the computer completely unusable. disk thrashing started around 5500000 objects. i don't have a massive amount of memory on my machine though. would testing for the amount of installed memory be a way of handling that, so as to know how many objects would be acceptable, to avoid excessive thrashing? i think i've read several times that finding out how much memory isn't feasible or at least isn't a good idea, not sure though. how could you find out how many objects is reasonable in memory at once?

What on earth are you trying to build? Are you building a closed system (you control everything) or a black box (you have no idea what will be on a system at any given time)? Does the "app" have a GUI or is it a service/daemon process, etc ? It looks like your trying to do data mining or visualization type stuff ?

Memory is always a moving target. It's better to let the OS handle the management of the memory and not try to second guess it by implementing a memory checking system.

By the way, the disk thrashing is the virtual memory system kicking and causing a lot of paging.

Remember! The more real (chips) memory you have the better your system will perform. If didn't already know, the virtual memory system lets you access more memory than you really have. That's why your system was choking. It was spending all of it's time trying to manage memory and swaping (paging).

I'm also a Cocoa newbie.......

good luck.

-tim

thanks very much, ben.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >find out maximum number of objects in memory at once? (From: Ben Dougall <email@hidden>)

  • Prev by Date: More Splash Screens
  • Next by Date: Re: More Splash Screens
  • Previous by thread: find out maximum number of objects in memory at once?
  • Next by thread: NSScanner reads the correct number but the number isn't added to an array
  • Index(es):
    • Date
    • Thread