Move trace events for CPU sampling to a debug
The CPU sampling profiler trace events were added on windows to investigate some strange patterns happening in the field. We have enough data to make some analysis over it. There are plan to add sampling profiler to renderers, io-thread and so on. This will increase the amount of trace events in a trace and it's better to avoid producing events that are not needed. We are moving these trace events to a debug category. This will allow us to make a specific slow-reports scenario if we still want to analyze the sampling profiler and it's behavior. R=wittman@chromium.org Change-Id: If348399336e60c4aa511ea783aec4c92d0575462 Reviewed-on: https://chromium-review.googlesource.com/c/1340908Reviewed-by:oysteine <oysteine@chromium.org> Reviewed-by:
Mike Wittman <wittman@chromium.org> Commit-Queue: Etienne Bergeron <etienneb@chromium.org> Cr-Commit-Position: refs/heads/master@{#609404}
Showing
Please register or sign in to comment