From: "J.Rinas" <jrinas@gmx.de>
To: nfs@lists.sourceforge.net
Subject: invalidate cache / NFS performance on a diskless system
Date: Thu, 9 Dec 2004 17:18:48 +0100 [thread overview]
Message-ID: <200412091718.48973.jrinas@gmx.de> (raw)
Hello!
We've set up our network using a linux 2.6.9 server and
abt. 25-30 linux clients using NFS.
The clients are booting through PXE and work in a diskless fashion.
i.e.=20
they mount their root directory via NFS
only /var and /tmp are on a tmpfs device.
To improve performance we have currently set the root directory=20
(including the /usr tree) to use the mount options
ro,
noatime,
v3,
rsize=3D32768,wsize=3D32768,
actimeo=3D180,
hard,tcp,nocto,nolock
To further improve the performance of the clients,=20
I'd like to increase actimeo to abt. 9 hours.
But this leads to severe problems, if some small configurations are done=20
during the day (e.g. installing new soft or configuration work...):
The changes do not apprear on the client nodes in reasonable time.
So I'd like to know if there is a switch to invalidate the whole NFS / VFS?=
=20
cache at once!
(e.g. an echo something > /proc/somewhere )?
An there any other hints/experiences to improve performance on such a syste=
m?
(Our new server with 10k rpm Disks is already ordered!)
tnx fr ur help
J=FCrgen
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2004-12-10 5:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 16:18 J.Rinas [this message]
2004-12-10 5:34 ` invalidate cache / NFS performance on a diskless system Trond Myklebust
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200412091718.48973.jrinas@gmx.de \
--to=jrinas@gmx.de \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.