Linux NFS development
 help / color / mirror / Atom feed
From: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>
To: linux-nfs <linux-nfs@vger.kernel.org>
Cc: Trond Myklebust <trond.myklebust@primarydata.com>
Subject: wrong latency info for flexfiles on layout return
Date: Tue, 6 Feb 2018 23:10:19 +0100 (CET)	[thread overview]
Message-ID: <1253710805.3166627.1517955019275.JavaMail.zimbra@desy.de> (raw)



Hi Trond et al.

by exploring data provided on layoutreturn I can see that some
information is wrong, in particular the IO latency completition
time for write:

{
   "iostats":[
      {
         "deviceAddr":"tcp://192.168.178.40.128.2",
         "duration":{
            "seconds":5,
            "nseconds":285924462
         },
         "readInfo":{
            "bytes":0,
            "latency":{
               "completitionTime":{
                  "seconds":0,
                  "nseconds":0
               },
               "bytesRequested":0,
               "opsCompleted":0,
               "busyTime":{
                  "seconds":0,
                  "nseconds":0
               },
               "opsRequested":0,
               "bytesCompleted":0,
               "bytesNotDelivered":0
            },
            "count":0
         },
         "fh":"01caffee00000000b1f9635e000d00000800000000000000050130",
         "writeInfo":{
            "bytes":624193536,
            "latency":{
               "completitionTime":{
                  "seconds":25737,
                  "nseconds":816217921
               },
               "bytesRequested":624193536,
               "opsCompleted":9526,
               "busyTime":{
                  "seconds":5,
                  "nseconds":224017937
               },
               "opsRequested":9526,
               "bytesCompleted":624193536,
               "bytesNotDelivered":0
            },
            "count":9526
         },
         "deviceId":"00000001000000000000000000000000",
         "open-stateid":"5a7a259b0000000100000004"
      }
   ]
}


you can see this with wireshark as well.

Regards,
   Tigran.

             reply	other threads:[~2018-02-06 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-06 22:10 Mkrtchyan, Tigran [this message]
2018-02-06 22:29 ` wrong latency info for flexfiles on layout return Trond Myklebust
2018-02-07  8:03   ` Mkrtchyan, Tigran
2018-02-07 11:54     ` Trond Myklebust

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=1253710805.3166627.1517955019275.JavaMail.zimbra@desy.de \
    --to=tigran.mkrtchyan@desy.de \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.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