New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 632459 link

Starred by 2 users
Status: Fixed
Owner:
█ w...@chromium.org
Last visit > 30 days ago
Closed: Aug 2016
Cc:
liber...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Add a metric for number of concurrent AVDAs/MediaCodecs

Project Member Reported by w...@chromium.org, Jul 28 2016 
I'm thinking concurrent AVDAs because it's trivial to get, and is almost 1:1 with MediaCodecs.

Probably just recording one sample every time we register an AVDA with the AVDATimer is easiest and answers the question of what the peak number is.
Project Member

Comment 1 by bugdroid1@chromium.org, Aug 3 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/c530313fcf3c4bb922317e2577136d3b68b52882

commit c530313fcf3c4bb922317e2577136d3b68b52882
Author: watk <watk@chromium.org>
Date: Wed Aug 03 00:15:30 2016

Add a histogram: Media.AVDA.NumAVDAInstances

NumAVDAInstances records the number of concurrently running
AndroidVideoDecodeAccelerators which is effectively equivalent to the
number of allocated MediaCodecs.

BUG= 632459 

Review-Url: https://codereview.chromium.org/2195443002
Cr-Commit-Position: refs/heads/master@{#409394}

[modify] https://crrev.com/c530313fcf3c4bb922317e2577136d3b68b52882/media/gpu/android_video_decode_accelerator.cc
[modify] https://crrev.com/c530313fcf3c4bb922317e2577136d3b68b52882/tools/metrics/histograms/histograms.xml

Comment 2 by w...@chromium.org, Aug 3 2016

Status: Fixed (was: Started)
►

Sign in to add a comment