Lowest latency is milliseconds

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • laurengrob
    Administrator
    • Jan 2021
    • 98

    Lowest latency is milliseconds

    Hi guys,

    I recognized that the scaling for latency seems to be wrong when you have all NVMe setup. Scale shows Milliseconds only and I doubt that I have peaks with some hundred ms latency on a R10 all nvme - and my vsphere shows me us latency for the NFS datastore coming from the QS.



    Is there any possibility to configure this?

    Cheers,
    Stefan
  • laurengrob
    Administrator
    • Jan 2021
    • 98

    #2
    Thanks Stefan, as your graph shows it looks like we're reporting the units incorrectly on that graph. We've got engineering looking into it and will post back here once we have more information. Just to confirm, that was the Storage Volume graph or the Storage Pool grapn?
    Best,
    Steve

    Comment

    • laurengrob
      Administrator
      • Jan 2021
      • 98

      #3
      Sorry for the late reply, seems I've missed the info mail (or got none). That's actually the behavior on all latency graphs I found, the screenshot was from the pool.

      Comment

      • laurengrob
        Administrator
        • Jan 2021
        • 98

        #4
        Thanks Stefan, we dug into it and the telegraph module that's collecting the data into the wtime and rtime counters in our influxdb is actually gathering information that's not true latency. It's some amalgamation of other counters. As such we're removing the "Latency" graph from the Storage Pool in the mean time and will be adding that back in later after we get a better handle on how to pull that information together using the lower level counters we get on a per device basis.

        The other change we're making it to make the Latency units across all Latency graphs in microseconds rather than milliseconds. So look for those changes in upcoming builds but for now you'll have to discount the information you're getting in the Storage Pool "Latency" graph you're seeing within QuantaStor 5.7.2 and older.

        Comment

        • laurengrob
          Administrator
          • Jan 2021
          • 98

          #5
          Thanks for the details Steve. I look forward to the changes.

          Cheers

          Comment

          Working...