I'm pretty sure nobody has ever used this. I didn't even when I was working on Project Candle and actively investigating power consumption in Firefox. As https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Power_profiling_overview says: > observations made during power profiling — even more than with other kinds of > profiling — can disturb what is being observed. For example, the Gecko > Profiler takes samples at 1000Hz using a timer. Each of these samples can > trigger a wakeup, which consumes power and obscures Firefox's natural wakeup > patterns. For this reason, integrating power measurements into the Gecko > Profiler is unlikely to be useful, and other power profiling tools typically > use much lower sampling rates (e.g. 1Hz.) Let's just remove the code.

Nobody has ever used this, and measuring power consumption while running a sampling profiler at 1000 Hz isn't a good idea.

Bug 769431 added this code, FWIW.

It's possible that Cleopatra should be updated as well.

Comment on attachment 8827364 [details] [diff] [review] Remove Intel Power Gadget integration from the compiler Review of attachment 8827364 [details] [diff] [review]: ----------------------------------------------------------------- You missed some stuff in ProfileEntry.cpp: mPower, POWER, and the 'p' profile buffer entries.

https://hg.mozilla.org/integration/mozilla-inbound/rev/7a0ca4bad5c3449b4f0ee22d66bc051f40f044fb Bug 1331571 - Remove Intel Power Gadget integration from the compiler. r=mstange.

Whoops, this bug and commit should have said "profiler" instead of "compiler". Oh well.