<?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 Interpreting Intel Memory Latency Checker Output. in Mobile and Desktop Processors</title>
    <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/Interpreting-Intel-Memory-Latency-Checker-Output/m-p/434769#M19358</link>
    <description>&lt;P&gt;I am using a dual socket Xeon E5- 2650 machine with 32 GB of memory (Numa Node). I have been wanting to determine&lt;/P&gt;&lt;P&gt;the memory latency for a CPU located in node 0 and memory allocated in node 1 and vice versa. Below is the output of MLC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;./mlc  –c0 –i9&lt;/P&gt;&lt;P&gt;Intel(R) Memory Latency Checker - v3.1a&lt;/P&gt;&lt;P&gt;Measuring idle latencies (in ns)...&lt;/P&gt;&lt;P&gt;                Numa node&lt;/P&gt;&lt;P&gt;Numa node            0       1&lt;/P&gt;&lt;P&gt;       0          69.4   118.4&lt;/P&gt;&lt;P&gt;       1         120.9    69.8&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Measuring Peak Memory Bandwidths for the system&lt;/P&gt;&lt;P&gt;Bandwidths are in MB/sec (1 MB/sec = 1,000,000 Bytes/sec)&lt;/P&gt;&lt;P&gt;Using all the threads from each core if Hyper-threading is enabled&lt;/P&gt;&lt;P&gt;Using traffic with the following read-write ratios&lt;/P&gt;&lt;P&gt;ALL Reads        :      84419.1&lt;/P&gt;&lt;P&gt;3:1 Reads-Writes :      78571.6&lt;/P&gt;&lt;P&gt;2:1 Reads-Writes :      77405.7&lt;/P&gt;&lt;P&gt;1:1 Reads-Writes :      76944.3&lt;/P&gt;&lt;P&gt;Stream-triad like:      71137.4&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Measuring Memory Bandwidths between nodes within system&lt;/P&gt;&lt;P&gt;Bandwidths are in MB/sec (1 MB/sec = 1,000,000 Bytes/sec)&lt;/P&gt;&lt;P&gt;Using all the threads from each core if Hyper-threading is enabled&lt;/P&gt;&lt;P&gt;Using Read-only traffic type&lt;/P&gt;&lt;P&gt;                Numa node&lt;/P&gt;&lt;P&gt;Numa node            0       1&lt;/P&gt;&lt;P&gt;       0        42956.4 20636.6&lt;/P&gt;&lt;P&gt;       1        20434.2 42859.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Measuring Loaded Latencies for the system&lt;/P&gt;&lt;P&gt;Using all the threads from each core if Hyper-threading is enabled&lt;/P&gt;&lt;P&gt;Using Read-only traffic type&lt;/P&gt;&lt;P&gt;Inject  Latency Bandwidth&lt;/P&gt;&lt;P&gt;Delay   (ns)    MB/sec&lt;/P&gt;&lt;P&gt;==========================&lt;/P&gt;&lt;P&gt; 00000  162.49    84301.1&lt;/P&gt;&lt;P&gt; 00002  161.99    84227.3&lt;/P&gt;&lt;P&gt; 00008  159.84    83922.1&lt;/P&gt;&lt;P&gt; 00015  156.98    83520.4&lt;/P&gt;&lt;P&gt; 00050  111.13    68611.6&lt;/P&gt;&lt;P&gt; 00100   99.14    50781.7&lt;/P&gt;&lt;P&gt; 00200   92.75    33050.8&lt;/P&gt;&lt;P&gt; 00300   89.26    24573.0&lt;/P&gt;&lt;P&gt; 00400   87.29    19625.5&lt;/P&gt;&lt;P&gt; 00500   85.81    16389.1&lt;/P&gt;&lt;P&gt; 00700   82.69    12398.8&lt;/P&gt;&lt;P&gt; 01000   82.53     9169.0&lt;/P&gt;&lt;P&gt; 01300   81.64     7352.0&lt;/P&gt;&lt;P&gt; 01700   80.25     5888.5&lt;/P&gt;&lt;P&gt; 02500   79.06     4325.2&lt;/P&gt;&lt;P&gt; 03500   78.10     3357.7&lt;/P&gt;&lt;P&gt; 05000   77.66     2613.2&lt;/P&gt;&lt;P&gt; 09000   76.99     1832.3&lt;/P&gt;&lt;P&gt; 20000   76.52     1289.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Measuring cache-to-cache transfer latency (in ns)...&lt;/P&gt;&lt;P&gt;Local Socket L2-&amp;gt;L2 HIT  latency        31.4&lt;/P&gt;&lt;P&gt;Local Socket L2-&amp;gt;L2 HITM latency        35.8&lt;/P&gt;&lt;P&gt;Remote Socket LLC-&amp;gt;LLC HITM latency (data address homed in writer socket)&lt;/P&gt;&lt;P&gt;                        Reader Numa Node&lt;/P&gt;&lt;P&gt;Writer Numa Node     0       1&lt;/P&gt;&lt;P&gt;            0        -   130.7&lt;/P&gt;&lt;P&gt;            1    129.4       -&lt;/P&gt;&lt;P&gt;Remote Socket LLC-&amp;gt;LLC HITM latency (data address homed in reader socket)&lt;/P&gt;&lt;P&gt;                        Reader Numa Node&lt;/P&gt;&lt;P&gt;Writer Numa Node     0       1&lt;/P&gt;&lt;P&gt;            0        -    80.5&lt;/P&gt;&lt;P&gt;            1     79.7       -&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From this, how can I get the desired latencies?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Wed, 05 Oct 2016 18:12:32 GMT</pubDate>
    <dc:creator>vvaib</dc:creator>
    <dc:date>2016-10-05T18:12:32Z</dc:date>
    <item>
      <title>Interpreting Intel Memory Latency Checker Output.</title>
      <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/Interpreting-Intel-Memory-Latency-Checker-Output/m-p/434769#M19358</link>
      <description>&lt;P&gt;I am using a dual socket Xeon E5- 2650 machine with 32 GB of memory (Numa Node). I have been wanting to determine&lt;/P&gt;&lt;P&gt;the memory latency for a CPU located in node 0 and memory allocated in node 1 and vice versa. Below is the output of MLC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;./mlc  –c0 –i9&lt;/P&gt;&lt;P&gt;Intel(R) Memory Latency Checker - v3.1a&lt;/P&gt;&lt;P&gt;Measuring idle latencies (in ns)...&lt;/P&gt;&lt;P&gt;                Numa node&lt;/P&gt;&lt;P&gt;Numa node            0       1&lt;/P&gt;&lt;P&gt;       0          69.4   118.4&lt;/P&gt;&lt;P&gt;       1         120.9    69.8&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Measuring Peak Memory Bandwidths for the system&lt;/P&gt;&lt;P&gt;Bandwidths are in MB/sec (1 MB/sec = 1,000,000 Bytes/sec)&lt;/P&gt;&lt;P&gt;Using all the threads from each core if Hyper-threading is enabled&lt;/P&gt;&lt;P&gt;Using traffic with the following read-write ratios&lt;/P&gt;&lt;P&gt;ALL Reads        :      84419.1&lt;/P&gt;&lt;P&gt;3:1 Reads-Writes :      78571.6&lt;/P&gt;&lt;P&gt;2:1 Reads-Writes :      77405.7&lt;/P&gt;&lt;P&gt;1:1 Reads-Writes :      76944.3&lt;/P&gt;&lt;P&gt;Stream-triad like:      71137.4&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Measuring Memory Bandwidths between nodes within system&lt;/P&gt;&lt;P&gt;Bandwidths are in MB/sec (1 MB/sec = 1,000,000 Bytes/sec)&lt;/P&gt;&lt;P&gt;Using all the threads from each core if Hyper-threading is enabled&lt;/P&gt;&lt;P&gt;Using Read-only traffic type&lt;/P&gt;&lt;P&gt;                Numa node&lt;/P&gt;&lt;P&gt;Numa node            0       1&lt;/P&gt;&lt;P&gt;       0        42956.4 20636.6&lt;/P&gt;&lt;P&gt;       1        20434.2 42859.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Measuring Loaded Latencies for the system&lt;/P&gt;&lt;P&gt;Using all the threads from each core if Hyper-threading is enabled&lt;/P&gt;&lt;P&gt;Using Read-only traffic type&lt;/P&gt;&lt;P&gt;Inject  Latency Bandwidth&lt;/P&gt;&lt;P&gt;Delay   (ns)    MB/sec&lt;/P&gt;&lt;P&gt;==========================&lt;/P&gt;&lt;P&gt; 00000  162.49    84301.1&lt;/P&gt;&lt;P&gt; 00002  161.99    84227.3&lt;/P&gt;&lt;P&gt; 00008  159.84    83922.1&lt;/P&gt;&lt;P&gt; 00015  156.98    83520.4&lt;/P&gt;&lt;P&gt; 00050  111.13    68611.6&lt;/P&gt;&lt;P&gt; 00100   99.14    50781.7&lt;/P&gt;&lt;P&gt; 00200   92.75    33050.8&lt;/P&gt;&lt;P&gt; 00300   89.26    24573.0&lt;/P&gt;&lt;P&gt; 00400   87.29    19625.5&lt;/P&gt;&lt;P&gt; 00500   85.81    16389.1&lt;/P&gt;&lt;P&gt; 00700   82.69    12398.8&lt;/P&gt;&lt;P&gt; 01000   82.53     9169.0&lt;/P&gt;&lt;P&gt; 01300   81.64     7352.0&lt;/P&gt;&lt;P&gt; 01700   80.25     5888.5&lt;/P&gt;&lt;P&gt; 02500   79.06     4325.2&lt;/P&gt;&lt;P&gt; 03500   78.10     3357.7&lt;/P&gt;&lt;P&gt; 05000   77.66     2613.2&lt;/P&gt;&lt;P&gt; 09000   76.99     1832.3&lt;/P&gt;&lt;P&gt; 20000   76.52     1289.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Measuring cache-to-cache transfer latency (in ns)...&lt;/P&gt;&lt;P&gt;Local Socket L2-&amp;gt;L2 HIT  latency        31.4&lt;/P&gt;&lt;P&gt;Local Socket L2-&amp;gt;L2 HITM latency        35.8&lt;/P&gt;&lt;P&gt;Remote Socket LLC-&amp;gt;LLC HITM latency (data address homed in writer socket)&lt;/P&gt;&lt;P&gt;                        Reader Numa Node&lt;/P&gt;&lt;P&gt;Writer Numa Node     0       1&lt;/P&gt;&lt;P&gt;            0        -   130.7&lt;/P&gt;&lt;P&gt;            1    129.4       -&lt;/P&gt;&lt;P&gt;Remote Socket LLC-&amp;gt;LLC HITM latency (data address homed in reader socket)&lt;/P&gt;&lt;P&gt;                        Reader Numa Node&lt;/P&gt;&lt;P&gt;Writer Numa Node     0       1&lt;/P&gt;&lt;P&gt;            0        -    80.5&lt;/P&gt;&lt;P&gt;            1     79.7       -&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From this, how can I get the desired latencies?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Oct 2016 18:12:32 GMT</pubDate>
      <guid>https://community.intel.com/t5/Mobile-and-Desktop-Processors/Interpreting-Intel-Memory-Latency-Checker-Output/m-p/434769#M19358</guid>
      <dc:creator>vvaib</dc:creator>
      <dc:date>2016-10-05T18:12:32Z</dc:date>
    </item>
    <item>
      <title>Re: Interpreting Intel Memory Latency Checker Output.</title>
      <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/Interpreting-Intel-Memory-Latency-Checker-Output/m-p/434770#M19359</link>
      <description>&lt;P&gt;In order to address any inquiry in regard to the Intel® Memory Latency Checker, you need to contact our Software developer team.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;A href="https://software.intel.com/en-us/forum"&gt;https://software.intel.com/en-us/forum&lt;/A&gt; &lt;A href="https://software.intel.com/en-us/articles/intelr-memory-latency-checker"&gt;https://software.intel.com/en-us/articles/intelr-memory-latency-checker&lt;/A&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;A href="https://software.intel.com/en-us/forum"&gt;https://software.intel.com/en-us/forum&lt;/A&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;Allan. &lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Oct 2016 19:16:18 GMT</pubDate>
      <guid>https://community.intel.com/t5/Mobile-and-Desktop-Processors/Interpreting-Intel-Memory-Latency-Checker-Output/m-p/434770#M19359</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2016-10-06T19:16:18Z</dc:date>
    </item>
  </channel>
</rss>

