Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site alliant.UUCP Path: utzoo!linus!alliant!rdr From: rdr@alliant.UUCP (Roger Roles) Newsgroups: net.micro.mac Subject: Re: Apple Hard Disk 20 Comments... Message-ID: <146@alliant.UUCP> Date: Mon, 30-Dec-85 11:05:25 EST Article-I.D.: alliant.146 Posted: Mon Dec 30 11:05:25 1985 Date-Received: Wed, 1-Jan-86 04:20:38 EST References: <186@decwrl.DEC.COM> Reply-To: rdr@alliant.UUCP (Roger Roles) Organization: Alliant Computer Systems, Acton, MA Lines: 27 Summary: Does the finder have to do everything at startup? In article <186@decwrl.DEC.COM> harrow@exodus.DEC (Jeff Harrow, NCSE LKG1-3/F16 DTN=226-7445) writes: >... >First and foremost, the speed of the FInder (V5.0) is ridiculous. >Now, I say this with some careful consideration as I realize that >with 13.7 Megabytes in 729 files, it is doing a LOT of work to >prepare the presentation of the desktop. HOWEVER, being a human >... Does the finder have to traverse the entire directory tree at startup in order to display the desktop? One of the major advantages of a tree structured directory organization is the distribution of compute cycles over several small units of information rather than over one large unit. The finder should only have to look at the top level of the directory structure (and any open folders) in order to display the desktop. Of course a drawback of this would be that some amount of overhead would be incurred by opening a folder, but this should be smaller and more distributed than looking at the entire directory structure at finder startup time. Have you tried finder 5.1xxx (I don't remember what xxx was, something like b9)? I'm wondering if it has any bug fixes/speed improvements. -- -- #include ...!{linus | mit-eddie}!alliant!rdr Roger D. Roles