On Jul 5, 2008, at 3:00 PM, Joan Lluch (casa) wrote:
Basically for performance reasons, the G. collector "preffers" to let memory usage grow (while it is still available) in order to avoid too many collections or to try that the user does not notice it, and in practice it generally succeeds at it. But you will definitely notice some annoying sporadic app response delays of half a second or so specially if your app is very complex and maintains lots of objects referencing each other in complex graphs.
Only if some of those objects force the main thread to block (which can happen as certain objects do require finalization on the main thread -- these are considered to be bugs and will be eliminated as time permits) or if you have written classes with complex finalizers that cause your secondary threads to block.
And it isn't that the collector "prefers" to let memory usage grow. More so that the collector strives to achieve a balance between memory use, responsiveness, and CPU cycles consumed, with user responsiveness being the most heavily weighted of the three.
If there are ways for the collector to collect more efficiently without impacting user responsiveness, said ways will be implemented....
b.bum
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
