Video metrics for playback failures |
||
Issue descriptionAt a high-level, we should add any necessary logging/metrics so we can answer the question, "how often do we fail at video playback and what are the top reasons?" From Hiro: We have three metrics for HW video decoder. Media.GpuVideoDecoderInitializeStatus Media.GpuVideoDecoderError Media.GpuArcVideoDecodeAccelerator.InitializeResult First two metrics are for pure Chrome video stack. The last one is for ARC++ video stack. But the three metrics Hiro listed don't provide a complete picture, hence filing this bug. We should add metrics to track video playback failures (in Chrome, ARC++, the media app, etc - for both software and hardware decoding) so we can detect regressions - i.e. we should track if there are any major spikes.
,
May 8 2018
,
May 9 2018
Issue 840697 has been merged into this issue.
,
May 15 2018
other metrics: Media.PipelineStatus.AudioVideo.H264.DDS.HW Media.PipelineStatus.AudioVideo.H264.SW Media.PipelineStatus.*.*.SW/HW. |
||
►
Sign in to add a comment |
||
Comment 1 by conradlo@chromium.org
, May 8 2018Components: OS>Kernel>Video