From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 02:36:34 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 7FE8F106567A for ; Tue, 29 Jun 2010 02:36:34 +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 69A1B8FC08 for ; Tue, 29 Jun 2010 02:36:33 +0000 (UTC) Received: (qmail 63649 invoked by uid 2000); 29 Jun 2010 02:36:32 -0000 Date: Mon, 28 Jun 2010 21:36:32 -0500 From: "Rick C. Petty" To: Jeremy Chadwick Message-ID: <20100629023632.GB63450@kay.kiwi-computer.com> References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628034741.GA45748@kay.kiwi-computer.com> <20100628045852.GA75380@icarus.home.lan> <20100628142025.GB52174@kay.kiwi-computer.com> <20100628145600.GA92144@icarus.home.lan> <20100628151835.GA53315@kay.kiwi-computer.com> <20100628162911.GA94456@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100628162911.GA94456@icarus.home.lan> User-Agent: Mutt/1.4.2.3i Cc: Rick Macklem , 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:36:34 -0000 On Mon, Jun 28, 2010 at 09:29:11AM -0700, Jeremy Chadwick wrote: > > # Increase send/receive buffer maximums from 256KB to 16MB. > # FreeBSD 7.x and later will auto-tune the size, but only up to the max. > net.inet.tcp.sendbuf_max=16777216 > net.inet.tcp.recvbuf_max=16777216 > > # Double send/receive TCP datagram memory allocation. This defines the > # amount of memory taken up by default *per socket*. > net.inet.tcp.sendspace=65536 > net.inet.tcp.recvspace=131072 I tried adjusting to these settings, on both the client and the server. I still see the same jittery/stuttery video behavior. Thanks for your suggestions though, these are probably good settings to have around anyway since I have 12 GB of RAM on the client and 8 GB of RAM on the server. > make.conf WITHOUT_IPV6 would affect ports, src.conf WITHOUT_INET6 would > affect the base system (thus rpcbind). The src.conf entry is what's > causing rpcbind to spit out the above "cannot get information" messages, > even though IPv6 is available in your kernel (see below). > > However: your kernel configuration file must contain "options INET6" or > else you wouldn't have IPv6 addresses on lo0. So even though your > kernel and world are synchronised, IPv6 capability-wise they probably > aren't. This may be your intended desire though, and if so, no biggie. Oh forgot about that. I'll have to add the "nooptions" since I like to build as close to GENERIC as possible. Mostly the WITHOUT_* stuff in /etc/src.conf is to reduce my overall build times, since I don't need some of those tools. I'm okay with the messages though; I'll probably comment out WITHOUT_INET6. Thanks again for your suggestions, -- Rick C. Petty