Re: Library loading policy on Mac OS X with Cocoa
Re: Library loading policy on Mac OS X with Cocoa
- Subject: Re: Library loading policy on Mac OS X with Cocoa
- From: Brian Hill <email@hidden>
- Date: Wed, 27 Jun 2001 08:27:52 -0500
On Tuesday, June 26, 2001, at 10:17 PM, Chris Hanson wrote:
I think there's probably a subtle, fundamental piece of
functionality that's broken in the application launch
functionality in Mac OS X. Once it's fixed I expect things will
get much better and we won't have to use silly hacks like lazy
loading of libraries and lazy import resolution to get it around
it. (I bet it's one of those performance bugs that's just spread
out enough that it's difficult to see with profiling too.)
I agree. My current suspect is DirectoryServices/lookupd. It seems
like something is hitting lookupd every time an application is
launched. It would also explain why you can't launch any
applications if lookupd has gone to lunch and can't talk to the
local NetInfo server (which it seems to about 6 times a week for
me). This can't help the launch speed any.
But I suppose that this is off topic...
Brian
email@hidden
http://personalpages.tds.net/~brian_hill
"Why? I came into this game for adventure - go anywhere, travel
light, get in, get out, wherever there's trouble, a man alone.
Now they've got the whole country sectioned off and you can't
move without a form. I'm the last of a breed."
-- Archibald "Harry" Tuttle, Rogue HVAC Repairman