From: Or Gerlitz <ogerlitz@voltaire.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: iostat "await" like counter for measuring nfs latency
Date: Tue, 27 Jul 2010 13:07:04 +0300 (IDT) [thread overview]
Message-ID: <Pine.LNX.4.64.1007271300180.2110@zuben.voltaire.com> (raw)
Doing some iscsi and nfs performance testing, I realized that iostat(1)
doesn't support an "await" (*) like counter for measuring nfs latency.
Can tracking nfs latency be done in other means? is there a plan to
extend the nfs iostats code to include such/similar counter?
thanks,
Or.
(*) await - The average time (in milliseconds) for I/O requests issued
to the device to be served. This includes the time spent by the
requests in queue and the time spent servicing them.
next reply other threads:[~2010-07-27 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 10:07 Or Gerlitz [this message]
2010-07-27 15:27 ` iostat "await" like counter for measuring nfs latency Trond Myklebust
2010-07-28 9:45 ` Or Gerlitz
2010-07-28 17:40 ` Chuck Lever
2010-07-28 19:21 ` Sebastien Godard
2010-07-29 15:53 ` Chuck Lever
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=Pine.LNX.4.64.1007271300180.2110@zuben.voltaire.com \
--to=ogerlitz@voltaire.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).