Add idle wakeups to chrome://tracing |
|||||||||||
Issue descriptionPipe idle wakeup metric from within Chrome (collected by the task manager backend) to chrome://tracing so that it fits into the TBMv2 perf tests. Do this on all the platforms that collect this metric.
,
May 26 2017
,
Jun 13 2017
,
Jun 13 2017
,
Jun 27 2017
,
Jun 27 2017
My plan is to get idle wakeups from GetIdleWakeupsPerSecond() in process_metrics.cc.
,
Jun 27 2017
Also related is Issue 649641.
,
Jun 28 2017
,
Sep 25 2017
,
Oct 23 2017
Note that on Windows ProcessMetrics::GetIdleWakeupsPerSecond() is not (yet) implemented. [18356:14996:1023/133635.411:ERROR:process_metrics.cc(105)] NOT IMPLEMENTED (Call Stack) > base.dll!base::ProcessMetrics::GetIdleWakeupsPerSecond() Line 105 C++ Symbols loaded. chrome.dll!performance_monitor::ProcessMetricsHistory::SampleMetrics() Line 82 C++ Symbols loaded. chrome.dll!performance_monitor::PerformanceMonitor::UpdateMetricsOnIOThread(int current_update_sequence) Line 200 C++ Symbols loaded.
,
Oct 23 2017
Will send a CL to disable for Windows later today, thanks for bringing it up!
,
Oct 26 2017
Issue 778526 has been merged into this issue.
,
Jan 24 2018
,
Apr 26 2018
Issue 794884 has been merged into this issue.
,
Aug 10
,
Nov 26
Bug creator has unassigned themselves. Does this still need to get done? If there are no replies in some time, the next triage from Speed Metrics should mark this as WontFix.
,
Nov 27
I believe perfetto plans to do this? Marking WontFix, as I don't think we'll be able to justify the effort anytime soon otherwise.
,
Nov 27
Yeah makes sense to punt to perfetto, as we're not looking to write a metric that uses this signal in the immediate future. |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by sullivan@chromium.org
, May 25 2017Components: Speed>Metrics