Return to BSD News archive
Newsgroups: comp.os.386bsd.misc Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!pipex!uknet!festival!edcogsci!richard From: richard@cogsci.ed.ac.uk (Richard Tobin) Subject: Re: Shared Library Status ? Message-ID: <CMApnr.3rB@cogsci.ed.ac.uk> Organization: HCRC, University of Edinburgh References: <hastyCM8Buv.26z@netcom.com> <michaelv.762936864@ponderous.cc.iastate.edu> <hastyCM9r6q.KFB@netcom.com> Date: Mon, 7 Mar 1994 13:04:38 GMT Lines: 21 In article <hastyCM9r6q.KFB@netcom.com> hasty@netcom.com (Amancio Hasty Jr) writes: >I have seen kernel compiles on my old 486DX33 (RIP) grow from >11 minutes with the old 386bsd plus patches to 22 + minutes under >a netbsd-current with shared-libraries. Well, there are rather a lot of variables there! For example, you've probably switched from gcc1 to gcc2. Building the kernel is a fairly bad case for shared libraries - lots of small(ish) compilations, each with several processes being started. In the past, I've found that the most noticeable effect of shared libraries (apart from saved disk space) is the greatly reduced time to link large X programs - writing out a 2Mb file under NFS takes several seconds. -- Richard -- Richard Tobin, HCRC, Edinburgh University R.Tobin@ed.ac.uk "Your monkey has got it right, sir." - HHGTTG