From: Raphael Clifford <cliffor@rockefeller.edu>
To: nfs@lists.sourceforge.net
Subject: jumbo frames and performance
Date: Mon, 17 Jun 2002 15:12:17 -0400 [thread overview]
Message-ID: <3D0E3491.10309@rockefeller.edu> (raw)
In-Reply-To: E17K1pY-00014i-00@usw-sf-list2.sourceforge.net
Would you mind explaining the two performance points below a bit further
and maybe putting them in the FAQ? They look very interesting.
Regarding the "sync" option, why does not having it incur extra costs
at the server?
Cheers,
Raphael
>It also looks like you are not using jumbo frames, which
>Trond has mentioned as a big performance boost for tcp in
>100 baseT full duplex environments.
>
>Also, since you're using 0.3.3 utils, I assume you are
>using sync exports; otherwise there are costs at the server
>which are hidden from the benchmark data.
>
>Tom
>
>
>
_______________________________________________________________
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next parent reply other threads:[~2002-06-17 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E17K1pY-00014i-00@usw-sf-list2.sourceforge.net>
2002-06-17 19:12 ` Raphael Clifford [this message]
2002-06-17 19:48 ` jumbo frames and performance Raphael Clifford
2002-06-17 21:13 ` Tom McNeal
2002-06-17 19:26 Lever, Charles
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=3D0E3491.10309@rockefeller.edu \
--to=cliffor@rockefeller.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox