It may have something to do with working set cache that Mac OS X can
maintain. On the first launch of an application no usable cache of the
working set exits so it likely loads in more pages then needed when
launched the first time (best guess). On secondary launches it has a
better picture of the working set needed at launch.
Leopard no longer does this working set caching (resulting in the
merry demise of the ever growing /var/vm/app_profiles directories on
my nightly compiler regression testing machines). The exact comment
with which my radar was closed was:
"Engineering has provided the following feedback regarding this issue:
There are no application profiles on Leopard. Similar (or better)
performance was achieved by using a more flexible read-ahead strategy."
Jonas
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-dev/email@hidden
