From owner-freebsd-smp Sat Dec 12 01:00:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04250 for freebsd-smp-outgoing; Sat, 12 Dec 1998 01:00:26 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA04229 for ; Sat, 12 Dec 1998 01:00:23 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 24046 invoked by uid 1001); 12 Dec 1998 09:00:10 +0000 (GMT) To: gus@Bourg.Net Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: gettimeofday/named In-Reply-To: Your message of "Fri, 11 Dec 1998 18:25:50 -0800 (PST)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 12 Dec 1998 10:00:10 +0100 Message-ID: <24044.913453210@verdi.nethelp.no> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have some FreeBSD-Current machines running named. I'm having a little > bit of a challenege with them, though. Named is taking up all of the CPU > on the machine. Some of these machines are running SMP kernels and some > aren't. Are you running the standard FreeBSD named (ie 8.1.2) from -current? How many zones do you have? > As you can see here, named isn't being very nice. :-) I did a ktrace on > it, and then a dump. Heres what I got: > 79892 named CALL gettimeofday(0xefbfda84,0) > 79892 named RET gettimeofday 0 > 79892 named CALL sendto(0x4,0x83fba80,0x1e,0,0x850d07c,0x10) > 79892 named GIO fd 4 wrote 30 bytes > "\M^B\^T\0\0\0\^A\0\0\0\0\0\0\bnocharge\^Cnet\0\0\^O\0\^A" > 79892 named RET sendto 30/0x1e > 79892 named CALL gettimeofday(0x8084b04,0) > 79892 named RET gettimeofday 0 > 79892 named CALL gettimeofday(0xefbfda84,0) > 79892 named RET gettimeofday 0 > 79892 named CALL sendto(0x4,0x83efe80,0x1e,0,0x8bcebec,0x10) > 79892 named GIO fd 4 wrote 30 bytes > "\M^B\^S\0\0\0\^A\0\0\0\0\0\0\bnocharge\^Cnet\0\0\^O\0\^A" I see long sequences of gettimeofday() right after a named restart - that's when it tries do get the SOA of every zone it's secondary for, to check that the zone is current. After it's finished verifying the zones, things get nice and quiet. You need to look at some longer traces, I think. Is named spending its time on system calls, or in userland? How many gettimeofday() calls do you have per second? Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message