From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 02:28:59 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67FBB106564A for ; Tue, 29 Jun 2010 02:28:59 +0000 (UTC) (envelope-from rick@svn.kiwi-computer.com) Received: from svn.kiwi-computer.com (174-20-59-6.mpls.qwest.net [174.20.59.6]) by mx1.freebsd.org (Postfix) with SMTP id E409D8FC08 for ; Tue, 29 Jun 2010 02:28:58 +0000 (UTC) Received: (qmail 63510 invoked by uid 2000); 29 Jun 2010 02:28:57 -0000 Date: Mon, 28 Jun 2010 21:28:57 -0500 From: "Rick C. Petty" To: Rick Macklem Message-ID: <20100629022857.GA63450@kay.kiwi-computer.com> References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628034741.GA45748@kay.kiwi-computer.com> <20100628153527.GB53315@kay.kiwi-computer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd2009@kiwi-computer.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 02:28:59 -0000 On Mon, Jun 28, 2010 at 10:09:21PM -0400, Rick Macklem wrote: > > > On Mon, 28 Jun 2010, Rick C. Petty wrote: > > > If it makes any difference, the server's four CPUs are > >pegged at 100% (running "nice +4" cpu-bound jobs). But that was the case > >before I enabled v4 server too. > > If it is practical, it would be interesting to see what effect killing > off the cpu bound jobs has w.r.t. performance. I sent SIGTSTP to all those processes and brought the CPUs to idle. The jittering/stuttering is still present when watching h264 video. So that rules out scheduling issues. I'll be investigating Jeremy's TCP tuning suggestions next. -- Rick C. Petty