Re: stochastic fair queueing in the elevator [Re: [BENCHMARK] 2.4.20-ck3 / aa / rmap with contest]

Valdis.Kletnieks@vt.edu
Mon, 10 Feb 2003 01:06:27 -0500


--==_Exmh_-154650848P
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, 10 Feb 2003 06:10:08 +0100, Jakob Oestergaard said:

> In stock 2.4.20 the interaction is horrible - whatever was done there i=
s
> not optimal. A 'tar xf' on the client will neither load the network
> nor the server - it seems to be network latency bound (readahead not
> doing it's job - changing min-readahead and max-readahead on the client=

> doesn't seem to make a difference). However, my desktop (running on the=

This sounds like the traditional NFS suckage that has been there for deca=
des.
The problem is that 'tar xf' ends up doing a *LOT* of NFS calls - a huge
stream of stat()/open()/chmod()/utime() calls. On a local disk, most of
this gets accelerated by the in-core inode cache, but on an NFS mount, yo=
u're
looking at lots and lots of synchronous calls.

In 'man 5 exports':

async This option allows the NFS server to violate the NFS pro=
tocol
and reply to requests before any changes made by that re=
quest
have been committed to stable storage (e.g. disc drive).

Using this option usually improves performance, but at the =
cost
that an unclean server restart (i.e. a crash) can cause da=
ta to
be lost or corrupted.

In releases of nfs-utils upto and including 1.0.0, this o=
ption
was the default. In this and future releases, sync i=
s the
default, and async must be explicit requested if needed.=
To
help make system adminstrators aware of this change, 'expo=
rtfs'
will issue a warning if neither sync nor async is specified=
=2E

Does this address your NFS issue?
-- =

Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech

--==_Exmh_-154650848P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+R0FjcC3lWbTT17ARAjYrAKDF/UowtexBnAueVAWK6eR+i4co2QCgmL4s
PTmZ//OGP2umXwV5s5yLhpU=
=dK1Q
-----END PGP SIGNATURE-----

--==_Exmh_-154650848P--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/