From owner-freebsd-current@FreeBSD.ORG Wed Apr 14 12:44:48 2004 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 DD77616A4CE for ; Wed, 14 Apr 2004 12:44:48 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9365043D1D for ; Wed, 14 Apr 2004 12:44:48 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i3EJilZI012176; Wed, 14 Apr 2004 14:44:47 -0500 (CDT) (envelope-from dan) Date: Wed, 14 Apr 2004 14:44:47 -0500 From: Dan Nelson To: Tim Kientzle Message-ID: <20040414194447.GD28745@dan.emsphone.com> References: <11095.1081621779@critter.freebsd.dk> <407B1EBC.6050405@freebsd.org> <407B234D.7070209@kientzle.com> <20040413160331.GM6308@numachi.com> <20040413200013.GC53327@cirb503493.alcatel.com.au> <6.0.1.1.1.20040414065121.039cde20@imap.sfu.ca> <407D78AB.1000700@kientzle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <407D78AB.1000700@kientzle.com> X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: Peter Jeremy cc: current@freebsd.org cc: Colin Percival Subject: Re: Optimizing RCng execution speed ? 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: Wed, 14 Apr 2004 19:44:49 -0000 In the last episode (Apr 14), Tim Kientzle said: > Colin Percival wrote: > >Out of the total 4.88 seconds the major consumers are: > > > > syslogd 0.89 s > > 2) What is syslogd doing for 0.89 seconds? > > I understand why mountcritlocal and fsck might take a while, but > syslogd doesn't strike me as an obvious slow point. (Unless it's > waiting on a DNS lookup? Can that be avoided with appropriate > /etc/hosts entries?) It is logging the kernel bootup output one line at a time, fsyncing between lines. This can take a LONG time if you were just in single-user mode and stored a lot of short shell lines in the kernel buffer. I just remove the SYNC_FILE flag from line 741. Why is kernel (and only kernel) log output fsynced anyway? -- Dan Nelson dnelson@allantgroup.com