<?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 An update for these energy in Software Tuning, Performance Optimization &amp; Platform Monitoring</title>
    <link>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076205#M5405</link>
    <description>&lt;P&gt;An update for these energy status counters for Intel Xeon processors E5 v3 and E5 v4 will be in the next SDM.&lt;/P&gt;</description>
    <pubDate>Thu, 09 Jun 2016 20:27:03 GMT</pubDate>
    <dc:creator>SHIH_K_Intel</dc:creator>
    <dc:date>2016-06-09T20:27:03Z</dc:date>
    <item>
      <title>Using RAPL to read PP0 and DRAM energy on haswell</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076202#M5402</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;

&lt;P&gt;According to the Intel's software developer's manual, RAPL allows up to read energy values for different domains. The PKG(0 or 1) which is the whole socket on a motherboard, &amp;nbsp;power plans PP0 and PP1 and the DRAM energy.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;I am trying to use that to read the Package energy and the DRAM and PP0 on a server mother board for a E5-2620 v3 (a Haswell xeon with 6 cores). I am using the PAPI component for RAPL.&lt;/P&gt;

&lt;P&gt;While I am getting meaningful numbers for both the&amp;nbsp;PACKAGE_ENERGY:PACKAGE0 and the&amp;nbsp;DRAM_ENERGY:PACKAGE0 , the PP0 is always returning zeros. which doesn't seem to me correct for a computationally intensive code given that PP0 is the cores power.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Any idea on &amp;nbsp;what &amp;nbsp;might be causing this? is there anything I need to turn on or off in my BIOS to read these values? any pointer to the solution is appreciated.&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Thank you,&lt;/P&gt;</description>
      <pubDate>Tue, 05 Apr 2016 22:47:57 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076202#M5402</guid>
      <dc:creator>Sameer_A_</dc:creator>
      <dc:date>2016-04-05T22:47:57Z</dc:date>
    </item>
    <item>
      <title>Intel has changed the</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076203#M5403</link>
      <description>&lt;P&gt;Intel has changed the implementation of RAPL without much documentation.&lt;/P&gt;

&lt;P&gt;For the Xeon E5 v3 there are two issues:&lt;/P&gt;

&lt;OL&gt;
	&lt;LI&gt;The only supported domains are "Package" and "DRAM"&lt;/LI&gt;
	&lt;LI&gt;The "Energy Unit" for DRAM is not the same as the value that is read from the RAPL unit register.&amp;nbsp;&amp;nbsp; Instead, Xeon E5 v3 processors use a DRAM Energy Unit of 15.3 microJoules.&amp;nbsp; (Ref:&amp;nbsp; "Intel Xeon Processor E5-1600/2400/2600/4600 v3 Product Families Datasheet, Volume 2: Registers", document 330784 -- section 5.3.2 in Revision 003).&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Mon, 11 Apr 2016 08:35:40 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076203#M5403</guid>
      <dc:creator>McCalpinJohn</dc:creator>
      <dc:date>2016-04-11T08:35:40Z</dc:date>
    </item>
    <item>
      <title>Thank your for your reply.</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076204#M5404</link>
      <description>&lt;P&gt;Thank your for your reply.&lt;/P&gt;

&lt;P&gt;About the energy unit for the DRAM. I think RAPL wraps that for you and gives you a counter that returns that in Jouls, it also gives you the actual count if you need, rapl:::DRAM_ENERGY:PACKAGE0 for jouls &amp;nbsp;and&amp;nbsp;rapl:::DRAM_ENERGY_CNT:PACKAGE0 for count.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Apr 2016 19:54:33 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076204#M5404</guid>
      <dc:creator>Sameer_A_</dc:creator>
      <dc:date>2016-04-11T19:54:33Z</dc:date>
    </item>
    <item>
      <title>An update for these energy</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076205#M5405</link>
      <description>&lt;P&gt;An update for these energy status counters for Intel Xeon processors E5 v3 and E5 v4 will be in the next SDM.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Jun 2016 20:27:03 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076205#M5405</guid>
      <dc:creator>SHIH_K_Intel</dc:creator>
      <dc:date>2016-06-09T20:27:03Z</dc:date>
    </item>
    <item>
      <title>Dear All,</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076206#M5406</link>
      <description>&lt;P&gt;Dear All,&lt;/P&gt;

&lt;P&gt;I am facing a similar problem with my Intel Core i7-6800k. I am getting &lt;STRONG&gt;All Zeros&amp;nbsp;&lt;/STRONG&gt;for DRAM and PP0. Even for the Package reading, I am getting a weird reading of 0.6 Watt and 1.9 J for an intensive program running for 3.3 seconds. I tried a longer benchmark running for 3 minutes but still getting 0.6 Watt and around 111 J.&lt;/P&gt;

&lt;P&gt;I get the same readings when I access the package energy register:&lt;/P&gt;

&lt;P&gt;/sys/class/powercap/intel-rapl/intel-rapl:0/energy_uj&lt;/P&gt;

&lt;P&gt;Any help would be appreciated&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Regards&lt;/P&gt;

&lt;P&gt;Mostafa&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2017 16:26:50 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076206#M5406</guid>
      <dc:creator>Mostafa_M_1</dc:creator>
      <dc:date>2017-02-02T16:26:50Z</dc:date>
    </item>
    <item>
      <title>In general, the DRAM RAPL</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076207#M5407</link>
      <description>&lt;P&gt;In general, the DRAM RAPL energy counter is only supported on "server" processors, not on "client" processors -- e.g., Section 14.9.5 of Volume 3 of the SW Developer's Manual.&lt;/P&gt;

&lt;P&gt;The PP0 domain seems to be deprecated on the server processors (some of the PP0 registers are still there, but return zero, while other PP0 registers no longer exist), so it is not surprising that it may no longer work on the client parts either.&lt;/P&gt;

&lt;P&gt;I have not seen problems with the Package-level RAPL counters on my Xeon E5 and Xeon Phi x200 systems...&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2017 17:36:48 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076207#M5407</guid>
      <dc:creator>McCalpinJohn</dc:creator>
      <dc:date>2017-02-02T17:36:48Z</dc:date>
    </item>
    <item>
      <title>I agree with John about the</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076208#M5408</link>
      <description>&lt;P&gt;I agree with John about the availability of PP0 domain availability&amp;nbsp;in non-server platforms, all what you can get is a Package reading (no finer grain readings possible).&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Weird number you are getting for the PKG reading can be explained by overflow probably, I am not sure how you are exactly reading the registers but RAPL doesn't protect against overflow in the numbers it provides. You might want to perform this test (provided by the PAPI wrapper) to get an idea:&amp;nbsp;https://github.com/tpatki/papi-rapl/blob/master/src/ctests/overflow.c&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2017 18:39:10 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076208#M5408</guid>
      <dc:creator>Sameer_A_</dc:creator>
      <dc:date>2017-02-02T18:39:10Z</dc:date>
    </item>
    <item>
      <title>Hi McCalpin,</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076209#M5409</link>
      <description>&lt;P&gt;Hi McCalpin,&lt;/P&gt;

&lt;P&gt;I know it's an old thread, but could you tell me where did you get the value as 15.3 micro-joule? I found some source code project hard coded this value in their source code as well. But as I searched in the latest Intel manual (changed in Dec 2016), The energy status unit is described like this:&lt;/P&gt;

&lt;P&gt;Energy Status Units&lt;/P&gt;

&lt;P&gt;&lt;BR /&gt;
	Energy related information (in Joules) is based on the multiplier,&lt;BR /&gt;
	1/2^ESU; where ESU is an unsigned integer represented by bits&lt;BR /&gt;
	12:8. Default value is 0EH (or 61 micro-joules)&lt;/P&gt;

&lt;P&gt;Thanks,&lt;/P&gt;

&lt;P&gt;Kenan&lt;/P&gt;</description>
      <pubDate>Mon, 13 Feb 2017 23:05:14 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076209#M5409</guid>
      <dc:creator>Kenan_L_</dc:creator>
      <dc:date>2017-02-13T23:05:14Z</dc:date>
    </item>
    <item>
      <title>The DRAM power unit is</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076210#M5410</link>
      <description>&lt;P&gt;The DRAM power unit is specified in Sections 5.3.2 and 5.3.3 of "Intel Xeon Processor E5-1600/2400/2600/4600 v3 Product Families Datasheet, Volume 2: Registers", document 330784, revision 003, June 2015.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Feb 2017 17:36:38 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076210#M5410</guid>
      <dc:creator>McCalpinJohn</dc:creator>
      <dc:date>2017-02-14T17:36:38Z</dc:date>
    </item>
    <item>
      <title>Hi McCalpin,</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076211#M5411</link>
      <description>&lt;P&gt;Hi McCalpin,&lt;BR /&gt;
	&lt;BR /&gt;
	On your first response you mention some characteristics for the case of the Xeon E5 processor, does it include Xeon E7 v3 processor as well?&amp;nbsp;&lt;BR /&gt;
	&lt;BR /&gt;
	As Sameer A. I am also interested in measuring DRAM energy consumption, and eventually throttle its bandwidth. According to some Intel tools (power_gov, and power_gadget), this can only be done if a specific setting is set in the BIOS but I don't seem to find this option.&lt;BR /&gt;
	&lt;BR /&gt;
	Thank you,&lt;BR /&gt;
	&lt;BR /&gt;
	Camilo&lt;/P&gt;</description>
      <pubDate>Mon, 10 Apr 2017 07:43:28 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076211#M5411</guid>
      <dc:creator>Camilo_Celis_G_</dc:creator>
      <dc:date>2017-04-10T07:43:28Z</dc:date>
    </item>
    <item>
      <title>For the Xeon E7, one could</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076212#M5412</link>
      <description>&lt;P&gt;For the Xeon E7, one could imagine searching for "Xeon E7 v3 datasheet" and looking in Section 5.3 of volume 2.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://www.intel.com/content/www/us/en/processors/xeon/xeon-e7-v3-datasheet-vol-2.html" target="_blank"&gt;http://www.intel.com/content/www/us/en/processors/xeon/xeon-e7-v3-datasheet-vol-2.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Apr 2017 21:21:12 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076212#M5412</guid>
      <dc:creator>McCalpinJohn</dc:creator>
      <dc:date>2017-04-10T21:21:12Z</dc:date>
    </item>
    <item>
      <title>Quote:Mostafa M. wrote:</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076213#M5413</link>
      <description>&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;Mostafa M. wrote:&lt;BR /&gt;&lt;P&gt;&lt;/P&gt;

&lt;P&gt;Dear All,&lt;/P&gt;

&lt;P&gt;I am facing a similar problem with my Intel Core i7-6800k. I am getting &lt;STRONG&gt;All Zeros&amp;nbsp;&lt;/STRONG&gt;for DRAM and PP0. Even for the Package reading, I am getting a weird reading of 0.6 Watt and 1.9 J for an intensive program running for 3.3 seconds. I tried a longer benchmark running for 3 minutes but still getting 0.6 Watt and around 111 J.&lt;/P&gt;

&lt;P&gt;I get the same readings when I access the package energy register:&lt;/P&gt;

&lt;P&gt;/sys/class/powercap/intel-rapl/intel-rapl:0/energy_uj&lt;/P&gt;

&lt;P&gt;Any help would be appreciated&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Regards&lt;/P&gt;

&lt;P&gt;Mostafa&lt;/P&gt;

&lt;P&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;

&lt;P&gt;Hi Mostafa,&lt;/P&gt;

&lt;P&gt;Have you been able to resolve the issue with the weird readings? I have the exact same issue on my i9-7900X CPU. I am getting very low power and energy values for the package when running a heavy workload (https://software.intel.com/en-us/forums/software-tuning-performance-optimization-platform-monitoring/topic/746959). I tried reading the rapl values with likwid, turbostat, perf, /sys/class/powercap, msrs, and the power numbers are way too low (up to 4W max).&amp;nbsp;&lt;/P&gt;

&lt;P&gt;As per Intel, my i9-7900X is a desktop CPU (https://www.intel.com/content/www/us/en/products/processors/core/x-series/i9-7900x.html) so I should not expect RAPL DRAM domain to work? Is that correct? Also, as per John's and Sameer's comments on PP0, only package domain should be available? Just making sure that what I see on my system is what I should expect, and I only see package-0. All the tools I use either report only package numbers or package and DRAM, where DRAM is always 0W.&lt;/P&gt;

&lt;P&gt;-Marko&lt;/P&gt;</description>
      <pubDate>Thu, 19 Oct 2017 20:49:19 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076213#M5413</guid>
      <dc:creator>Marko_S_</dc:creator>
      <dc:date>2017-10-19T20:49:19Z</dc:date>
    </item>
    <item>
      <title>Hi,</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076214#M5414</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I have been able to resolve the low energy reading issue by resetting the BIOS settings to default.&lt;/P&gt;

&lt;P&gt;&lt;A href="https://software.intel.com/en-us/forums/software-tuning-performance-optimization-platform-monitoring/topic/746959#comment-1914284" target="_blank"&gt;https://software.intel.com/en-us/forums/software-tuning-performance-optimization-platform-monitoring/topic/746959#comment-1914284&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Oct 2017 18:21:46 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Using-RAPL-to-read-PP0-and-DRAM-energy-on-haswell/m-p/1076214#M5414</guid>
      <dc:creator>Marko_S_</dc:creator>
      <dc:date>2017-10-30T18:21:46Z</dc:date>
    </item>
  </channel>
</rss>

