From: William Lee Irwin III <wli@holomorphy.com>
To: nfs@lists.sourceforge.net
Subject: performance much improved
Date: Sat, 6 Apr 2002 23:29:45 -0800 [thread overview]
Message-ID: <20020407072945.GN30807@holomorphy.com> (raw)
Earlier in the 2.4.x series I noted a strange anomaly:
NetBSD nfsroot clients were able to drive up the load on a 2.4.x NFS
server to 10 or 20. This was doubly surprising as the clients were
machines of far lesser power than the NFS server (e.g. sun3/60 vs. a
600MHz Athlon running Linux ~2.4.8).
A pleasant surprise occurred today while doing make build simultaneously
on all 3 of my NetBSD toasters (sun3/60, ss1, and decstation 5000/200):
The load average on my main machine (the NFS server, 2.4.18-pre7-ac3)
remained quite low, and the machine quite responsive.
I confess I haven't been following the developments closely, but I can
say thank you, and congratulations on the performance improvement.
Cheers,
Bill
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2002-04-07 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-07 7:29 William Lee Irwin III [this message]
2002-04-15 20:04 ` NFS Utils package Tom McNeal
2002-04-16 11:36 ` Ed V. Bartosh
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=20020407072945.GN30807@holomorphy.com \
--to=wli@holomorphy.com \
--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.