From owner-freebsd-current@FreeBSD.ORG Mon Nov 24 16:43:30 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFCC316A4CE for ; Mon, 24 Nov 2003 16:43:30 -0800 (PST) Received: from smtp1.server.rpi.edu (smtp1.server.rpi.edu [128.113.2.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id E207643FE3 for ; Mon, 24 Nov 2003 16:43:29 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp1.server.rpi.edu (8.12.10/8.12.9) with ESMTP id hAP0hT7P026468 for ; Mon, 24 Nov 2003 19:43:29 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <16322.26365.159173.946033@grasshopper.cs.duke.edu> References: <16322.26365.159173.946033@grasshopper.cs.duke.edu> Date: Mon, 24 Nov 2003 19:43:27 -0500 To: freebsd-current@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) Subject: Re: 40% slowdown with dynamic /bin/sh X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Nov 2003 00:43:31 -0000 At 3:15 PM -0500 11/24/03, Andrew Gallatin wrote: >Here is a simple test which times the execution of a null >shell script. It basically times fork/exec of the chosen >shell. >So.. forking a dynamic sh is roughly 40% more expensive >than forking a static copy of sh. This is embarrassing. To be more precise: shell scripts which do-nothing will be 40% more expensive than they used to be. It is not like the entire operating system will get 40% slower. >I propose that we at least make /bin/sh static. I suggest that we leave all of /bin and /sbin as it is for 5.2-release. We are still telling users that 5.2 is a snapshot of "-current", and it is more valuable to have a wider range of experience with this worst-case scenario. ("worst-case" == all files dynamically linked). We certainly may want to make changes to address the performance issues that you note, but there is no reason we must decide *which* change should be made right now. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu