From owner-freebsd-net@FreeBSD.ORG Sat Feb 1 01:20:01 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2975B96A; Sat, 1 Feb 2014 01:20:01 +0000 (UTC) Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E2A7A1CA7; Sat, 1 Feb 2014 01:20:00 +0000 (UTC) Received: by mail-ie0-f179.google.com with SMTP id ar20so4977053iec.10 for ; Fri, 31 Jan 2014 17:20:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=S5aYt//r4llUtWOUnBsX/w7f4ApMl+41Eh8RwIVf65s=; b=eHYjYbP/vEfYlRhYyANgSY1Ee9HEvpj8KE0Kfkjlriz0x0nGCX5sD4M5K574/o4BQ3 UC750yAC0JCYvMqBnj2BH0gk3C7fn97XmNVck/amSksH7Tvj6qDNfMDIsT1bJWhiF1KX gFE2WRmnOpDGeZ1X4ZRq+FYmXRmyU3PUBGXzRYK/dXx4Lb0LBLJMVYbNXfl5Ps4JIm66 JfbU08s1M0AUqbOJojMfrIgsdxH9VfnlzvI65k3QftHggL8HMpNfzlLHJ5Bv4JFV1rXc B/lXxte2RHxgLRrLqzq7uvhlC6DAItCTiqrVcKPaXYzWeIrrnjFNjLWKNzTTe91Q/MH5 TfhQ== MIME-Version: 1.0 X-Received: by 10.50.60.105 with SMTP id g9mr1447813igr.14.1391217600360; Fri, 31 Jan 2014 17:20:00 -0800 (PST) Sender: jdavidlists@gmail.com Received: by 10.42.170.8 with HTTP; Fri, 31 Jan 2014 17:20:00 -0800 (PST) In-Reply-To: <1622306213.1079665.1391210205488.JavaMail.root@uoguelph.ca> References: <1622306213.1079665.1391210205488.JavaMail.root@uoguelph.ca> Date: Fri, 31 Jan 2014 20:20:00 -0500 X-Google-Sender-Auth: fACMXLJidVL3k7PeVpegChTlAJY Message-ID: Subject: Re: Terrible NFS performance under 9.2-RELEASE? From: J David To: Rick Macklem Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org, Garrett Wollman X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Feb 2014 01:20:01 -0000 On Fri, Jan 31, 2014 at 6:16 PM, Rick Macklem wrote: > You can certainly try "-o rsize=61440,wsize=61440" (assuming a 4K page size) > for the mount, if you'd like. This has previously been tested with all 4k steps between 16k and 32k. All of them perform worse than With 61440, NFS fails outright on the random read test: $ iozone -e -I -s 1g -r 4k -i 0 -i 2 Iozone: Performance Test of File I/O Version $Revision: 3.420 $ Compiled for 64 bit mode. Build: freebsd [...] Include fsync in write timing O_DIRECT feature enabled File size set to 1048576 KB Record Size 4 KB Command line used: iozone -e -I -s 1g -r 4k -i 0 -i 2 Output is in Kbytes/sec Time Resolution = 0.000005 seconds. Processor cache size set to 1024 Kbytes. Processor cache line size set to 32 bytes. File stride size set to 17 * record size. random random bkwd record stride KB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread 1048576 4 24688 23891 Error reading block at 1073729536 read: Bad file descriptor Upon using the -w option, which leaves the file intact on exit, it's possible to see that it's not even 1gig in length: $ ls -aln iozone.tmp -rw-r----- 1 1000 0 1073709056 Feb 1 01:18 iozone.tmp It's 32k short, which is a pretty surprising result. Thanks!