<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Measurement of Disk Latency in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Measurement-of-Disk-Latency/m-p/37967#M1424</link>
    <description>&lt;P&gt;when we looked at &lt;STRONG&gt;perform &lt;/STRONG&gt;metrics  there is a big difference  as compared to the metrics reported by dynatrace .Can you please comment on that ?&lt;/P&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 09 Dec 2019 20:53:09 GMT</pubDate>
    <dc:creator>vaibhav_s_singh</dc:creator>
    <dc:date>2019-12-09T20:53:09Z</dc:date>
    <item>
      <title>Measurement of Disk Latency</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Measurement-of-Disk-Latency/m-p/37965#M1422</link>
      <description>&lt;P&gt;From Frank: Do you know how disk&lt;BR /&gt;latency is measured by Dynatrace? For example, does dynatrace measure direct or&lt;BR /&gt;cached access? Ioping?&lt;/P&gt;</description>
      <pubDate>Wed, 28 Sep 2022 09:42:20 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Measurement-of-Disk-Latency/m-p/37965#M1422</guid>
      <dc:creator>anton_goosen</dc:creator>
      <dc:date>2022-09-28T09:42:20Z</dc:date>
    </item>
    <item>
      <title>Re: Measurement of Disk Latency</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Measurement-of-Disk-Latency/m-p/37966#M1423</link>
      <description>&lt;P&gt;Disk latency reporting depends on OS level metrics specific to Linux and Windows. The reporting is passive and reflects the load generated by the active applications. It is not a "benchmark" tool as ioping seems to be. It should not reflect OS disk cache or buffers but only actual "disk drive" I/O. Of course the drive itself may (actually always does) have a cache and such latency component would be included and averaged over. Also, if the drive is some kind of virtual drive (as is usually the case in VMs) then the latency is still reported from the point of view of the host (VM) OS and may not map directly into any physical hard drive latency.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Oct 2017 13:53:30 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Measurement-of-Disk-Latency/m-p/37966#M1423</guid>
      <dc:creator>Grzegorz_Pawelc</dc:creator>
      <dc:date>2017-10-04T13:53:30Z</dc:date>
    </item>
    <item>
      <title>Re: Measurement of Disk Latency</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Measurement-of-Disk-Latency/m-p/37967#M1424</link>
      <description>&lt;P&gt;when we looked at &lt;STRONG&gt;perform &lt;/STRONG&gt;metrics  there is a big difference  as compared to the metrics reported by dynatrace .Can you please comment on that ?&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 09 Dec 2019 20:53:09 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Measurement-of-Disk-Latency/m-p/37967#M1424</guid>
      <dc:creator>vaibhav_s_singh</dc:creator>
      <dc:date>2019-12-09T20:53:09Z</dc:date>
    </item>
    <item>
      <title>Re: Measurement of Disk Latency</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Measurement-of-Disk-Latency/m-p/37968#M1425</link>
      <description>I'm not sure which metrics you mean? Do you refer to Windows Performance Monitor?&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Dec 2019 08:07:24 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Measurement-of-Disk-Latency/m-p/37968#M1425</guid>
      <dc:creator>Grzegorz_Pawelc</dc:creator>
      <dc:date>2019-12-10T08:07:24Z</dc:date>
    </item>
  </channel>
</rss>

