Re: Leopard performance penalty (3x slower), NSPopAutoreleasePool
Re: Leopard performance penalty (3x slower), NSPopAutoreleasePool
- Subject: Re: Leopard performance penalty (3x slower), NSPopAutoreleasePool
- From: Jon Hess <email@hidden>
- Date: Sat, 17 Nov 2007 19:37:10 -0800
Running your application with Leopard's Instruments.app and the object
alloc instrument should make what's going on clear.
Run your app and when you see the big run up in the memory graph,
select that range of time and see what object is being allocated more
than expected.
Jon Hess
On Nov 17, 2007, at 10:53 AM, Gerd Knops <email@hidden>
wrote:
I have a complex Cocoa application, 10.4 SDK (no GC etc). Loading a
document (and performing a large number of calculations triggered by
that) takes 4 seconds under Tiger.
Under Leopard, loading the same document takes 8 seconds until it
displays, after which the application is unresponsive for another 4
seconds, the entire time being spent in NSPopAutoreleasePool.
I presume that performance penalty is largely due to Leopards more
complex memory handling. Has anybody else observed this, and knows
of any strategies to minimize that overhead?
Thanks
Gerd
_______________________________________________
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
_______________________________________________
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