From akriman@darwin.helios.nd.edu Fri Nov 30 14:23:11 2001 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAUMN6n73708 for ; Fri, 30 Nov 2001 14:23:06 -0800 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Fri Nov 30 14:23:05 2001 -0800 Received: from mailspool.helios.nd.edu (mailspool.helios.nd.edu [129.74.250.7]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAUMN5B12554 for ; Fri, 30 Nov 2001 14:23:05 -0800 Received: from darwin.helios.nd.edu (darwin.helios.nd.edu [129.74.250.114]) by mailspool.helios.nd.edu (8.9.2/8.9.2) with ESMTP id RAA06007 for ; Fri, 30 Nov 2001 17:23:04 -0500 (EST) Received: (from akriman@localhost) by darwin.helios.nd.edu (8.10.1/8.10.1/ND-cluster) id fAUMN3b14938 for classics@u.washington.edu; Fri, 30 Nov 2001 17:23:03 -0500 (EST) Date: Fri, 30 Nov 2001 17:23:03 -0500 (EST) From: Alfred M Kriman Message-Id: <200111302223.fAUMN3b14938@darwin.helios.nd.edu> To: classics@u.washington.edu Subject: Re: Mac OS 10 improvements When comparing Macintosh operating systems, it is not fair (so far as I know still *) to compare the speed of the original OS with that of a later user-installed OS. The reason is that Macs, unlike PC's (+), have toolbox functions and other high-use pieces of the OS in ROM. When you install a new OS from disk, any modification of functions originally in ROM introduces two kinds of delay: (a) An initial start-up delay, as OS code is loaded from (usually) disk into RAM (which is, or at least is treated as volatile). To play it safe and for practical reasons, modified systems may bypass large chunks of ROM OS, so even minor system upgrades may put substantial code in RAM and noticeably degrade performance for this reason and those described under (b)... (b) Generally slower operation of every program (including most applications; nonmasochist programmers call system functions rather than reinvent the wheel and the dialog box). There are multiple reasons for the slower performance: less RAM is available for application code and data, sometimes forcing the machine to page-swap. RAM is usually slower than ROM (_always_ slower, at a given level of fabrication technology). There are additional communication traffic delays that depend in detail on the architecture, which tends to be optimized for original-OS-in-ROM. (*) I haven't been a regular Mac user in five years, but I think the preceding is still accurate. (+) By PC's, I mean generic machines that use Microsoft or similar OS's. These have traditionally used much less ROM, mostly for BIOS, afaik. There is no technical reason why the machine designer couldn't use the Mac ROM-intensive strategy (Atari also did it), but there are costs. Lisa had a GUI but used multiple OS's, and so had less OS in ROM. AMK .