http://lapcatsoftware.com/blog/2006/10/10/filling-an-nsmutablearray/ Coding under the close supervision of cats Fri, 09 Jul 2010 18:22:20 +0000 hourly 1 http://wordpress.org/?v=3.0 http://lapcatsoftware.com/blog/2006/10/10/filling-an-nsmutablearray/comment-page-1/#comment-19 Jeff Wed, 18 Oct 2006 20:08:23 +0000 http://lapcatsoftware.com/blog/2006/10/10/filling-an-nsmutablearray/#comment-19 When I add the same object repeatedly, it makes it up to 536 million before dying. An array of that many 4-byte pointers would take up about 2GB; I have no idea what other overhead an NSArray has. The system and the app will also consume memory. Perhaps it's reaching 4GB, though I've deliberately turned off everything else before the test. Anyway, <code>NSNotFound</code> is still safe. When I add the same object repeatedly, it makes it up to 536 million before dying. An array of that many 4-byte pointers would take up about 2GB; I have no idea what other overhead an NSArray has. The system and the app will also consume memory. Perhaps it’s reaching 4GB, though I’ve deliberately turned off everything else before the test. Anyway, NSNotFound is still safe.

]]> http://lapcatsoftware.com/blog/2006/10/10/filling-an-nsmutablearray/comment-page-1/#comment-17 Jeffstyr Wed, 18 Oct 2006 08:43:30 +0000 http://lapcatsoftware.com/blog/2006/10/10/filling-an-nsmutablearray/#comment-17 The amount of physical RAM you have shouldn't matter--it's the size of your virtual address space which does. For a 32-bit process, the limit is 4GB--you're probably running into that limit (unless you run out of swap space first). You should be able to get to a higher number if you just add the same NSNumber instance to your array over-and-over, rather than creating a new one each time through the loop--those are probably eating up the majority of your memory. The amount of physical RAM you have shouldn’t matter–it’s the size of your virtual address space which does. For a 32-bit process, the limit is 4GB–you’re probably running into that limit (unless you run out of swap space first). You should be able to get to a higher number if you just add the same NSNumber instance to your array over-and-over, rather than creating a new one each time through the loop–those are probably eating up the majority of your memory.

]]> http://lapcatsoftware.com/blog/2006/10/10/filling-an-nsmutablearray/comment-page-1/#comment-7 Jeff Tue, 10 Oct 2006 22:56:35 +0000 http://lapcatsoftware.com/blog/2006/10/10/filling-an-nsmutablearray/#comment-7 I'm only guessing that a Mac Pro couldn't handle it either. I'd be interested in hearing about real tests. I’m only guessing that a Mac Pro couldn’t handle it either. I’d be interested in hearing about real tests.

]]>