Linux NFS development
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Adrian von Bidder <avbidder-xzBkAS4TQxQfv37vnLkPlQ@public.gmane.org>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, nfs@lists.sourceforge.net
Subject: Re: [NFS] NFS performance debugging
Date: Wed, 25 Jun 2008 09:20:51 -0400	[thread overview]
Message-ID: <1214400051.7225.4.camel@localhost> (raw)
In-Reply-To: <200806250902.42880-xzBkAS4TQxQfv37vnLkPlQ@public.gmane.org>

On Wed, 2008-06-25 at 09:02 +0200, Adrian von Bidder wrote:
> On Tuesday 24 June 2008 22.29:31 J. Bruce Fields wrote:
> > On Tue, Jun 24, 2008 at 12:17:24PM +0200, Adrian von Bidder wrote:
> 
> > > Starting KDE, opening documents, sometimes also closing oo.org and
> > > saving documents takes several seconds longer than on local disk.
> >
> > "close" on nfs is an operation that requires a round-trip to the server
> > and waiting for the disk to commit any writes made before the close, so
> > if you've got to do a lot of those it can take time.  Fooling with the
> > journaling on the exported filesystem may help.
> 
> Are there tools to measure latencies on NFS?  Given a network dump, desired 
> output would be histograms of latencies by file operation?  (Or maybe I can 
> catch the information on the client, VFS side instead of NFS?

You can catch the info on the client. See the 'nfs-iostat' tool in the
latest nfs-utils git tree:

  http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=summary

Trond


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
    http://vger.kernel.org/vger-lists.html#linux-nfs


  parent reply	other threads:[~2008-06-25 13:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 14:59 [NFS] NFS performance debuggins Adrian von Bidder
     [not found] ` <200806231659.58158-xzBkAS4TQxQfv37vnLkPlQ@public.gmane.org>
2008-06-23 15:15   ` Trond Myklebust
2008-06-23 19:28   ` J. Bruce Fields
2008-06-24 10:17     ` [NFS] NFS performance debugging Adrian von Bidder
     [not found]       ` <200806241217.29243-xzBkAS4TQxQfv37vnLkPlQ@public.gmane.org>
2008-06-24 20:29         ` J. Bruce Fields
2008-06-25  7:02           ` Adrian von Bidder
     [not found]             ` <200806250902.42880-xzBkAS4TQxQfv37vnLkPlQ@public.gmane.org>
2008-06-25 13:20               ` Trond Myklebust [this message]
2008-06-25 13:59                 ` Steve Dickson
     [not found]                   ` <48624F34.1070108-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-06-27  7:30                     ` Krishna Kumar2
2008-06-27 13:44                       ` Chuck Lever
     [not found]                         ` <76bd70e30806270644j3e67c83and7b1f7fd6cc2f5f5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-27 18:12                           ` Trond Myklebust
2008-06-30  9:05                           ` Krishna Kumar2
2008-06-27 18:06                       ` Olga Kornievskaia
2008-06-25 16:56               ` J. Bruce Fields
2008-06-26  6:19                 ` Adrian von Bidder
     [not found]                   ` <200806260819.35108-xzBkAS4TQxQfv37vnLkPlQ@public.gmane.org>
2008-06-26 17:03                     ` J. Bruce Fields
2008-06-27  6:24                       ` Adrian von Bidder
     [not found]                         ` <200806270824.54066-xzBkAS4TQxQfv37vnLkPlQ@public.gmane.org>
2008-06-27 17:47                           ` J. Bruce Fields

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=1214400051.7225.4.camel@localhost \
    --to=trond.myklebust@fys.uio.no \
    --cc=avbidder-xzBkAS4TQxQfv37vnLkPlQ@public.gmane.org \
    --cc=bfields@fieldses.org \
    --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