From: Dean Hildebrand <seattleplus@gmail.com>
To: ntwrkd <ntwrkd@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS performance / diagnostic profiling with TCP
Date: Thu, 07 Aug 2008 19:16:12 -0700 [thread overview]
Message-ID: <489BAC6C.5090801@gmail.com> (raw)
In-Reply-To: <f257b9ab0807151118x5dec64aei73c284c9954fcfb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
ntwrkd wrote:
> Does anyone have some methods for doing diagnostic / performance
> profiling while using NFS over TCP?
>
Using tcpdump with tcptrace is really handy.
You do something like:
tcpdump -s 100 -w /tmp/tcpdump.out host <hostname>
tcptrace -Sl /tmp/tcpdump.out
xplot /tmp/a2b_tsg.xpl
One very important thing to remember, if you are interested in how the
tcp window is scaling, is to start tcpdump before you mount the server.
The tcp window size depends on a scaling factor that it gets when the
tcp connection is created (which is at mount time).
Dean
> Thanks in advance,
> Matthew Sacks
> matthewsacks.com
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-08-08 2:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 18:18 NFS performance / diagnostic profiling with TCP ntwrkd
[not found] ` <f257b9ab0807151118x5dec64aei73c284c9954fcfb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-15 18:31 ` Andrew Bell
2008-07-16 0:29 ` Shehjar Tikoo
2008-08-08 2:16 ` Dean Hildebrand [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-15 18:38 ntwrkd
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=489BAC6C.5090801@gmail.com \
--to=seattleplus@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=ntwrkd@gmail.com \
/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