From: "David B. Ritch" <dritch@hpti.com>
To: Matthew Mitchell <matthew@geodev.com>
Cc: NFS mailing list <nfs@lists.sourceforge.net>
Subject: Re: mmap() and NFS server performance
Date: 14 Dec 2002 11:51:23 -0500 [thread overview]
Message-ID: <1039884683.2767.29.camel@localhost> (raw)
In-Reply-To: <3DFA4C9A.50101@geodev.com>
When we moved some nfs clients from 2.4.18 to 2.4.20, we saw some
performance issues that initially appeared to be an nfs problem.
However, it turned out that the upgrade apparently broke autonegotiation
between the NICs in the nodes and our network switches. This did not
turn up immediately in network testing with tools such as netperf,
because we still had good one-way bandwidth with the nodes set to full
duplex and the switches set to half. However, two-way traffic
immediately caused lots of problems.
I never trust autonegotiation, and turn it off whenever I can.
You may be experiencing a similar problem.
dbr
On Fri, 2002-12-13 at 16:09, Matthew Mitchell wrote:
> Hello,
>
> We've noticed some interesting behavior regarding mmap file IO and were
> wondering if anyone here had some clues as to what might be going on.
--
David B. Ritch
High Performance Technologies, Inc.
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2002-12-14 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 21:09 mmap() and NFS server performance Matthew Mitchell
2002-12-13 21:35 ` Brian Pawlowski
2002-12-14 11:22 ` Trond Myklebust
2002-12-16 14:33 ` Matthew Mitchell
2002-12-16 14:50 ` Trond Myklebust
2002-12-16 20:04 ` Matthew Mitchell
2002-12-14 16:51 ` David B. Ritch [this message]
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=1039884683.2767.29.camel@localhost \
--to=dritch@hpti.com \
--cc=matthew@geodev.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.