Date: Wed, 14 Apr 2004 14:44:47 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Tim Kientzle <tim@kientzle.com> Cc: Colin Percival <colin.percival@wadham.ox.ac.uk> Subject: Re: Optimizing RCng execution speed ? Message-ID: <20040414194447.GD28745@dan.emsphone.com> In-Reply-To: <407D78AB.1000700@kientzle.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040414194447.GD28745>