A count of the number of seconds taken is not very useful.
However, Instruments (formerly Xray) or Shark should tell you exactly
what is going on and why things are taking time.
You need to do some spelunking and compare the times coming out of
Instruments or Shark in each OS.
And FWIW, if you haven't enabled garbage collection, I don't believe
Leopard does anything more sophisticated memory-wise than Tiger.
On Nov 17, 2007, at 10:53 AM, Gerd Knops 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
