From owner-freebsd-questions Wed Aug 2 15:59:46 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id PAA04372 for questions-outgoing; Wed, 2 Aug 1995 15:59:46 -0700 Received: from aero.org (aero.org [130.221.16.2]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id PAA04366 for ; Wed, 2 Aug 1995 15:59:44 -0700 Received: from antares.aero.org ([130.221.192.46]) by aero.org with SMTP id <111177-3>; Wed, 2 Aug 1995 15:43:56 -0700 Received: from anpiel.aero.org by antares.aero.org (4.1/AMS-1.0) id AA22729 for freebsd-questions@freebsd.org; Wed, 2 Aug 95 15:15:57 PDT To: freebsd-questions@freebsd.org Subject: Re: 2.0.5 Eager to go into swap Date: Wed, 2 Aug 1995 15:15:27 -0700 From: "Mike O'Brien" Message-Id: <95Aug2.154356pdt.111177-3@aero.org> Sender: questions-owner@freebsd.org Precedence: bulk Garrett sez: > Actually, the same `lorder ${OBJS} | tsort' technique ought to have > some beneficial effect. This doesn't group together commonly-used > routines, but it does group modules near each other based on > dependency. I remember when 'symorder' was first hacked together at Rand. I think you guys still use it. The whole purpose was to speed up things like 'ps' by preverting the order of symbols, so the ones 'ps' needed were at the front of the symbol table of /vmunix. Seems to me that you could get 90% of the win for 10% of the effort by doing something similar for libraries. You all pretty much know what the common routines are, and if you don't, then profiling random utilities and editors for a couple of days will tell you. Then just put those names in a file and create a simple utility that orders the library so the files containing those routines are together. Mike O'Brien