Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!mit-eddie!uw-beaver!tektronix!sequent!parsons From: parsons@sequent.UUCP (Ron V. Parsons) Newsgroups: comp.arch Subject: Re: Fastest Kernel Make Message-ID: <2877@sequent.UUCP> Date: Thu, 3-Sep-87 14:37:29 EDT Article-I.D.: sequent.2877 Posted: Thu Sep 3 14:37:29 1987 Date-Received: Sat, 5-Sep-87 16:58:32 EDT References: <26853@sun.uucp> Reply-To: parsons@sequent.UUCP (Ron V. Parsons) Organization: Sequent Computer Systems, Beaverton, OR Lines: 72 Keywords: Making kernel = (or) != speed of machine I'm Ron Parsons, the Technical Marketing Manager for Sequent Computers Renu Raman of Sun Microsystems referred to me talking about kernel make numbers. Here is some more data on the subject: Building the DYNIX system represents a significant amount of work. The DYNIX system includes all of 4.2bsd (with parallel enhancements) and much of AT&T System V Release 2.2. There are almost 6000 files in the DYNIX binary distribution. Of these, over 3000 must be compiled from C source, almost 300 must be interpreted by make and 60 must be directly assembled. There are almost 4000 compilations and assemblies and over 600 invocations of the nroff text formatter to build the on-line documentation. Low-effort, large-grained parallelization of the make utility reduced the time required to build the DYNIX system on the Balance 8000 computer by a factor of seven point five from the single-stream version of make. Table 1 shows the DYNIX system build times on a VAX(tm)11/750 and on various hardware configurations of the Balance 8000 sys- tem. The percentage of CPU usage indicates how well the build is utilizing the available resources. As expected, highly parallel builds use a greater percentage of the available CPU time in both monoprocessor and multiprocessor confi- gurations. Table 1 DYNIX 2.0 build times and CPU usage _______________________________________________________________________________ | | Single-stream | Modest parallelism| Maximal parallelism| | | (-P1) | (-P2) | (-P4) | |Config |__________|________|__________|_________|__________|__________| | | Time | CPU use| Time | CPU use | Time | CPU use | | | (hh:mm) | | (hh:mm) | | (hh:mm) | | |______________|__________|________|__________|_________|__________|__________| | VAX11/750 | 30:25 | 85% | 28:00 | 94% | - | - | |______________|__________|________|__________|_________|__________|__________| | Balance 8000 | 22:30 | 90% | - | - | - | - | | with 1 proc | | | | | | | |______________|__________|________|__________|_________|__________|__________| | Balance 8000 | - | - | 10:42 | 185% | - | - | | with 2 proc | | | | | | | |______________|__________|________|__________|_________|__________|__________| | Balance 8000 | - | - | 5:30 | 374% | 4:14 | 505% | | with 6 procs | | | | | | | |______________|__________|________|__________|_________|__________|__________| | Balance 8000 | - | - | - | - | 3:03 | 711% | | with 12 procs| | | | | | | |______________|__________|________|__________|_________|__________|__________| This table presents the build times (in real time) for the VAX11/750 and for various configurations of the Balance 8000 system. The percent CPU usage for each build is also given. The VAX11/750 configuration includes 8 Mbytes of memory and Fujitsu Eagle disks. The Balance 8000 configurations in- clude 10 Mbytes of memory and Fujitsu Eagle disks. The -P values indicate the relative amounts of parallelism for each build CPU usage for multiprocessor configurations reflects the percentage of a single CPU (i.e. 505% CPU use in a 6 proces- sor system is equivalent to 100% usage of 5.05 CPUs).