From owner-freebsd-current Wed Oct 11 20:53:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by hub.freebsd.org (Postfix) with ESMTP id 4337637B502 for ; Wed, 11 Oct 2000 20:53:23 -0700 (PDT) Received: from waterblue.imgsrc.co.jp (localhost [127.0.0.1]) by waterblue.imgsrc.co.jp (8.11.0/8.11.0) with ESMTP id e9C3fTG00863 for ; Thu, 12 Oct 2000 12:41:30 +0900 (JST) Date: Thu, 12 Oct 2000 12:41:29 +0900 Message-ID: <7mn1gaenfa.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: current@FreeBSD.ORG Subject: RE: -current grinds exceeding slow In-Reply-To: In your message of "11 Oct 2000 18:43:14 GMT" References: User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 12) (Channel Islands) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11 Oct 2000 18:43:14 GMT, John Baldwin wrote: > I don't know. Can you try to narrow down the date by cvsupping or > cvs updating with date tags to see when it started slowing down? I've checked with -D '2000-10-03 00:00:00 GMT' and -D '2000-10-04 12:00:00 GMT'. With previous kernel, "time find /usr/obj" returns 65 seconds, but with later kernel, it returns 547 seconds (/usr/obj is NFS mounted from localhost). Top command shows many processes locked with MUTEX status. It seems this is caused by jasone's commit at 3rd Oct... -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message