From owner-freebsd-fs@FreeBSD.ORG  Thu May  2 23:43:23 2013
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 4D74E1E1
 for <freebsd-fs@freebsd.org>; Thu,  2 May 2013 23:43:23 +0000 (UTC)
 (envelope-from scrappy@hub.org)
Received: from hub.org (hub.org [200.46.208.146])
 by mx1.freebsd.org (Postfix) with ESMTP id 1BE3D1C4C
 for <freebsd-fs@freebsd.org>; Thu,  2 May 2013 23:43:22 +0000 (UTC)
Received: from maia.hub.org (unknown [200.46.151.189])
 by hub.org (Postfix) with ESMTP id 1269E1F8AE2B;
 Thu,  2 May 2013 20:43:21 -0300 (ADT)
Received: from hub.org ([200.46.208.146])
 by maia.hub.org (mx1.hub.org [200.46.151.189]) (amavisd-maia, port 10024)
 with ESMTP id 10003-02; Thu,  2 May 2013 23:43:20 +0000 (UTC)
Received: from [10.5.250.150] (remote.ilcs.sd63.bc.ca [142.31.148.2])
 by hub.org (Postfix) with ESMTPA id 295D31F8AE2A;
 Thu,  2 May 2013 20:43:19 -0300 (ADT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: NFS Performance issue against NetApp
From: "Marc G. Fournier" <scrappy@hub.org>
In-Reply-To: <20130502221857.GJ32659@physics.umn.edu>
Date: Thu, 2 May 2013 16:43:17 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <420165EE-BBBF-4E97-B476-58FFE55A52AA@hub.org>
References: <834305228.13772274.1367527941142.JavaMail.root@k-state.edu>
 <75CB6F1E-385D-4E51-876E-7BB8D7140263@hub.org>
 <20130502221857.GJ32659@physics.umn.edu>
To: Graham Allan <allan@physics.umn.edu>
X-Mailer: Apple Mail (2.1503)
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2013 23:43:23 -0000


On 2013-05-02, at 15:18 , Graham Allan <allan@physics.umn.edu> wrote:

> On Thu, May 02, 2013 at 02:05:38PM -0700, Marc G. Fournier wrote:
>>=20
>> The thing is, I'm not convinced it is a NFS related issue =85 there =
are *so* many other variables involved =85 it could be something with =
the network stack =85 it could be something with the scheduler =85 it =
could be =85 hell, it could be like the guy states in that blog posting =
(http://antibsd.wordpress.com/) and be the compiler changes =85=20
>=20
> I'm just watching interestedly from the sidelines, and I hesitate to =
ask
> because it seems too obvious - maybe I missed something - but have you
> run both tests (Linux and FreeBSD) purely with local disk, to get a
> baseline independent of NFS?

Hadn't thought to do so with Linux, but =85

Linux =85=85. 20732ms, 20117ms, 20935ms, 20130ms, 20560ms
FreeBSD .. 28996ms, 24794ms, 24702ms, 23311ms, 24153ms

In the case of the following, I umount the file system, change the =
settings, mount and then run two runs:

FreeBSD, nfs, vfs.nfs.prime_access_cache=3D1 =85  279207ms, 273970ms
FreeBSD, nfs, vfs.nfs.prime_access_cache=3D0 =85 279254ms, 274667ms
FreeBSD, oldnfs, vfs.nfs.prime_access_cache=3D0 =85 244955ms, 243280ms
FreeBSD, oldnfs, vfs.nfs.prime_access_cache =3D1 =85 242014ms, 242393ms

Default for vfs.nfs.prime_access_cache appears to be 0 =85