Issue metadata
Sign in to add a comment
|
Analyze and reduce noise in gpu graphics memory measurements |
||||||||||||||||||||||||
Issue descriptionAccording to the analysis on all system health stories [1], the gpu graphics memory tend to be the noisiest across most stories. The distribution of values for this metric is tightly bimodal, with measurements clustering around two different values. For example on browse:news:cricbuzz [2], one of the largest offenders, from 100 samples we observe on the metric: 'by_os:gpu_memory:graphics:proportional_resident' A) 7.6 MiB on 32 samples B) 15.2 MiB on 68 samples Example traces for each of the measurements are: A) https://console.developers.google.com/m/cloudstorage/b/chromium-telemetry/o/trace-file-id_73-2017-06-14_22-12-49-89116.html B) https://console.developers.google.com/m/cloudstorage/b/chromium-telemetry/o/trace-file-id_72-2017-06-14_22-12-47-52078.html [1]: https://colab.corp.google.com/v2/notebook#fileId=0B586tdnIdbhKTDd2SHUwa2tCT1U [2]: https://colab.corp.google.com/v2/notebook#fileId=0B586tdnIdbhKQkN2aTdBYzlSVHM
,
Jun 21 2017
,
Jun 23 2017
,
Aug 2 2017
perezju@, does the work in issue 734853 address this?
,
Aug 2 2017
,
Aug 7 2017
The recommendation to reduce gpu noise recommended in issue 734853 was tried in issue 737353 , but got reverted since it did not yield any improvements. TL;DR from crbug.com/737353#c39 , something in the range [1], before my fix landed, caused the noise in gpu metrics to reduce significantly. And my CL did not have any effect after that. [1]: http://test-results.appspot.com/revision_range?start=477936&end=481246 I think I'll do a new analysis of noise soon to figure out what the current situation is.
,
Aug 15 2017
,
Aug 23 2017
,
Aug 30 2017
The noise situation gpu/cc has somewhat improved since my attempt in #7. I'm going to close this one in favor of the blocking issues instead: issue 734853 - the longer term solution for gpu/cc is to trigger memory dumps from within Chrome at appropriate times. issue 733894 - the catch-all issue where overall efforts on noise reduction will be tracked; now focusing on java_heap, which has become the worst offender since the improvements in gpu/cc. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by perezju@chromium.org
, Jun 21 2017