From owner-freebsd-fs@FreeBSD.ORG Sat Feb 28 08:20:04 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 929B11065670 for ; Sat, 28 Feb 2009 08:20:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 80CFD8FC08 for ; Sat, 28 Feb 2009 08:20:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n1S8K4BI061487 for ; Sat, 28 Feb 2009 08:20:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1S8K4xm061486; Sat, 28 Feb 2009 08:20:04 GMT (envelope-from gnats) Date: Sat, 28 Feb 2009 08:20:04 GMT Message-Id: <200902280820.n1S8K4xm061486@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Martin Birgmeier Cc: Subject: Re: kern/131360: [nfs] poor scaling behavior of the NFS server under load X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Martin Birgmeier List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Feb 2009 08:20:04 -0000 The following reply was made to PR kern/131360; it has been noted by GNATS. From: Martin Birgmeier To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/131360: [nfs] poor scaling behavior of the NFS server under load Date: Sat, 28 Feb 2009 09:16:44 +0100 (CET) To add to what Peter Keel is writing: My kernels *did* still use the 4BSD scheduler, so I am quite sure that Peter will not see an improvement when switching to it from the ULE scheduler. Next observation: My server, aside from serving NFS, is also serving samba clients. Yesterday, from a single Windows 98 host, a directory on the server containing approx. 100 files was deleted. During this time, the server was completely unresponsive (except that I could still ping it). It was not even possible to contact the DNS server running on it. After a few minutes (and presumably when the Windows 98 host was finished deleting the directory, I did not watch this directly), things returned to normal. However, the "xload" display from the server then refreshed again and indicated a truly gigantic load peak - it must have been greater than 50 as the background of the xload window was completely filled with y axis lines (the horizontal lines dividing load levels). Something has been messed up horribly with multiprocessing on 7.1.