Chromium Code Reviews| Index: tools/metrics/histograms/histograms.xml |
| diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml |
| index c0998a73beee328f6b7cf0b466011a72773fe2a4..53ca2079537cc9eb3bbf396583b31374ef153f58 100644 |
| --- a/tools/metrics/histograms/histograms.xml |
| +++ b/tools/metrics/histograms/histograms.xml |
| @@ -11363,6 +11363,18 @@ other types of suffix sets. |
| </summary> |
| </histogram> |
| +<histogram name="PerformanceMonitor.AverageCPU.BrowserProcess" |
| + units="PercentCPUUsage"> |
| + <summary> |
| + Average CPU utilization of the browser process, read out at each two-minute |
| + interval. On Windows this is a range from 0-100% of the total CPU capacity, |
|
Alexei Svitkine (slow)
2013/10/24 15:48:12
Update comment now that its consistent between pla
oystein (OOO til 10th of July)
2013/10/24 15:51:45
Done.
|
| + i.e. a quadcore system with one core running fully loaded and the other |
| + three idle would read as 25%. On non-Windows systems there's a 0-100% range |
| + per CPU, which is then summed up. I.e. a quadcore system fully loaded would |
| + read as 400%. |
| + </summary> |
| +</histogram> |
| + |
| <histogram name="PerformanceMonitor.HighCPU.BrowserProcess" enum="BooleanHit"> |
| <summary> |
| The number of times a browser process has continuously stayed above a |