From owner-freebsd-performance@FreeBSD.ORG Wed Feb 20 13:08:31 2008 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6EF0216A400 for ; Wed, 20 Feb 2008 13:08:31 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from ns.trinitel.com (186.161.36.72.static.reverse.ltdomains.com [72.36.161.186]) by mx1.freebsd.org (Postfix) with ESMTP id 2384113C458 for ; Wed, 20 Feb 2008 13:08:31 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from proton.storspeed.com (209-163-168-124.static.tenantsolutions.net [209.163.168.124] (may be forged)) (authenticated bits=0) by ns.trinitel.com (8.14.1/8.14.1) with ESMTP id m1KD8RIP070335; Wed, 20 Feb 2008 07:08:30 -0600 (CST) (envelope-from anderson@freebsd.org) Message-ID: <47BC264B.8010308@freebsd.org> Date: Wed, 20 Feb 2008 07:08:27 -0600 From: Eric Anderson User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Claus Guttesen References: <27dbfc8c0802190243y113d3059yd0c602850a4dbd6b@mail.gmail.com> <47BB33AD.1050005@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on ns.trinitel.com Cc: "freebsd-performance@freebsd.org" , freebsd-questions , Valerio Daelli Subject: Re: Bad performance of 7.0 nfs client with Solaris nfs server X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Feb 2008 13:08:31 -0000 Claus Guttesen wrote: >>> we have a FreeBSD 7.0 NFS client (csup today, built world and kernel). >>> It mounts a Solaris 10 NFS share. >>> We have bad performance with 7.0 (3MB/s). >>> We have tried both UDP and TCP mounts, both sync and async. >>> This is our mount: >>> >>> nest.xx.xx:/data/export/hosts/bsd7.xx.xx/ /mnt/nest.xx.xx nfs >>> noatime,async,-i,rw,-T,-3 >>> >>> Both our server (7.0 and Solaris 10) are Gigabit Ethernet, both are HP >>> Proliant DL360 i386 (NIC bge0): > > I have a solaris 9 nfs-server (on sparc) with som TB on HDS attached > to it with two qlogic-hba's. These partitions are shared to our > webservers via nfs, according to my mrtg-graph I get approx. 8 MB/s at > peak. I can probably get more but the requirement is not there. > > With four-way-servers and FreeBSD 6.2 I had a read- and write-size of > 8192. I ended up with this size by copying to and from the nfs-server > until I didn't get "nfs server not responding; is alive again" > message. Then I upgraded to FreeBSD 7.0 in October 2007 on a new > eight-way-server I started to get "not responding; alive again" during > load. So I decreased rw-size to the current 2048. > > When I decreased the size I also avoided another problem (by accident > :-) ). When uploading images I sometimes saw ImageMagick's convert > went into an (almost) infinite loop, comsuming 100 % cpu (on one core) > until killed. Reducing the rw-size eliminated this issue. > > fstab-entry: > > my.nfs.server:/archive /archive nfs > rw,nfsv3,-w=2048,-r=2048 0 0 > > I'm using udp-mounts, does not appear to change performance for my part. > > HTH. If FreeBSD is your NFS server, you should increase the number of nfsd threads to help with the "not responding" error. I usually run one nfsd thread per active client. Eric