From owner-freebsd-hackers@FreeBSD.ORG  Mon Apr 30 08:58:03 2012
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 63776106567F
	for <freebsd-hackers@freebsd.org>; Mon, 30 Apr 2012 08:58:03 +0000 (UTC)
	(envelope-from peterjeremy@acm.org)
Received: from mail11.syd.optusnet.com.au (mail11.syd.optusnet.com.au
	[211.29.132.192])
	by mx1.freebsd.org (Postfix) with ESMTP id E8BE98FC1D
	for <freebsd-hackers@freebsd.org>; Mon, 30 Apr 2012 08:58:02 +0000 (UTC)
Received: from server.vk2pj.dyndns.org
	(c220-239-251-180.belrs5.nsw.optusnet.com.au [220.239.251.180])
	by mail11.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id
	q3U8vpCa028814
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 30 Apr 2012 18:57:54 +1000
X-Bogosity: Ham, spamicity=0.000000
Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1])
	by server.vk2pj.dyndns.org (8.14.5/8.14.4) with ESMTP id q3U8voKl057774;
	Mon, 30 Apr 2012 18:57:50 +1000 (EST)
	(envelope-from peter@server.vk2pj.dyndns.org)
Received: (from peter@localhost)
	by server.vk2pj.dyndns.org (8.14.5/8.14.5/Submit) id q3U8vnJj057773;
	Mon, 30 Apr 2012 18:57:49 +1000 (EST) (envelope-from peter)
Date: Mon, 30 Apr 2012 18:57:48 +1000
From: Peter Jeremy <peterjeremy@acm.org>
To: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl>
Message-ID: <20120430085748.GA56921@server.vk2pj.dyndns.org>
References: <alpine.BSF.2.00.1204272201440.6369@wojtek.tensor.gdynia.pl>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="FL5UXtIhxfXey3p5"
Content-Disposition: inline
In-Reply-To: <alpine.BSF.2.00.1204272201440.6369@wojtek.tensor.gdynia.pl>
X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: freebsd-hackers@freebsd.org
Subject: Re: NFS - slow
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Apr 2012 08:58:03 -0000


--FL5UXtIhxfXey3p5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 2012-Apr-27 22:05:42 +0200, Wojciech Puchar <wojtek@wojtek.tensor.gdynia=
=2Epl> wrote:
>is there any way to speed up NFS server?
=2E..
>- write works terribly. it performs sync on every write IMHO,

You don't mention which NFS server or NFS version you are using but
for "traditional" NFS, this is by design.  The NFS server is stateless
and NFS server failures are transparent (other than time-wise) to the
client.  This means that once the server acknowledges a write, it
guarantees the client will be able to later retrieve that data, even
if the server crashes.  This implies that the server needs to do a
synchronous write to disk before it can return the acknowledgement
back to the client.

--=20
Peter Jeremy

--FL5UXtIhxfXey3p5
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iEYEARECAAYFAk+eVAwACgkQ/opHv/APuIdWawCfQIu5AmRgRr0g3wEBK6HCsBka
/jsAn0LY1oK+kJejZR4eiRsVWK6JdWOG
=peTt
-----END PGP SIGNATURE-----

--FL5UXtIhxfXey3p5--