Date: Mon, 28 Jun 2010 21:28:57 -0500 From: "Rick C. Petty" <rick-freebsd2009@kiwi-computer.com> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? Message-ID: <20100629022857.GA63450@kay.kiwi-computer.com> In-Reply-To: <Pine.GSO.4.63.1006282208070.836@muncher.cs.uoguelph.ca> References: <20100627221607.GA31646@kay.kiwi-computer.com> <Pine.GSO.4.63.1006271949220.3233@muncher.cs.uoguelph.ca> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628034741.GA45748@kay.kiwi-computer.com> <Pine.GSO.4.63.1006280032180.2680@muncher.cs.uoguelph.ca> <20100628153527.GB53315@kay.kiwi-computer.com> <Pine.GSO.4.63.1006282208070.836@muncher.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100629022857.GA63450>