Refactor GPU Process Lifetime histogram calls
Use the UMA histogram functions instead of macros for the GPU.ProcessLifetimeEvents.* metrics. This way the histogram calls for the different GPU modes can be combined. Also combine the three crash counters into |recent_crash_count_|, and reset it to zero when a new GPU mode is crashing. The histogram functions are slightly slower than the histogram macros because they don't cache the histogram object at the callsite. These calls are made once during GPU process startup and once following a crash, so they don't occur on a performance critical path. Bug: 1005383, 1030757 Change-Id: I98aee0d50852794270c1c9b4c156e013080d23a3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1961067 Commit-Queue: Sean Gilhuly <sgilhuly@chromium.org> Reviewed-by:Zhenyao Mo <zmo@chromium.org> Reviewed-by:
kylechar <kylechar@chromium.org> Cr-Commit-Position: refs/heads/master@{#724719}
Showing
Please register or sign in to comment