From owner-freebsd-fs@FreeBSD.ORG Wed Mar 28 21:36:55 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B8572106564A for ; Wed, 28 Mar 2012 21:36:55 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 6703E8FC16 for ; Wed, 28 Mar 2012 21:36:55 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap8EAPyCc0+DaFvO/2dsb2JhbABFhUC0NIIJAQEBAwEBAQEgKyALBRYYAgINGQIpAQkmBggHBAEZAwSHZAULqF2SG4EviUMFhQOBGASTNoIrgRGPHIMDgTgI X-IronPort-AV: E=Sophos;i="4.75,333,1330923600"; d="scan'208";a="162715640" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 28 Mar 2012 17:35:47 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 929B2B3F97; Wed, 28 Mar 2012 17:35:47 -0400 (EDT) Date: Wed, 28 Mar 2012 17:35:47 -0400 (EDT) From: Rick Macklem To: Sven Brandenburg Message-ID: <1023490904.1870197.1332970547582.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <4F709A18.50907@crashme.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - IE8 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@freebsd.org Subject: Re: NFSv3, ZFS, 10GE performance X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Mar 2012 21:36:55 -0000 Sven Brandenburg wrote: > On 03/26/2012 12:37 PM, Ivan Voras wrote: > > You could try modifying the rsize and wsize NFS options (read > > mount_nfs(8)), they help with UFS. > > I tried this a few days ago and fiddling rsize alters performance from > "ok" to "terrible". > However, you made me revisit this and mount_nfs(8) seems to have a gem > in its options: readahead. > This did the trick for me and my (long and sequential) reads. > While the manpage says its limited to 0-4, the best results were > achieved with readahead=8 : 1.1GB/s - which is what I had hoped for. > Yea, the new NFS client allows a readahead of up to 16. The man page for FreeBSD-9 should probably be changed, since the new NFS client is the default. Btw, without readahead, the client will do Read RPCs serially. (In other words, the next Read RPC won't start until the reply to the previous one has been received.) > On a tangent: gnu-dd 1GB/s is 10^9 Bytes/s, not 2^30. Yes, I fell for > it > at first :) > The good news is that there was no fiddling on the NFS server side. > (Apart from MTU increases, PCI settings and more buffers to get TCP > performance to full tilt in the first place) > > Hopefully, readahead doesn't kill performance for smaller files.. :-) > Well, readaheads only happen if the file is large enough for the readahead to be before EOF. As such, they just won't happen for small files. rick > regards, > Sven > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"