New issue
Advanced search Search tips

Issue 608510 link

Starred by 1 user
Status: Verified
Owner:
rtoy@chromium.org
Closed: May 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug

Blocking:
issue 564276



Sign in to add a comment

Add UMA reporting for webaudio hardware buffer size and callback buffer size

Project Member Reported by rtoy@chromium.org, May 2 2016 
In preparation of adding the AudioContext latency hint, it's useful to have measurements on the actual low latency buffer size from the HW and also the callback buffer size that is actually used by the context.

This is also important as we tune the callback buffer size on Android.  The current heuristics on Android causes a much larger buffer size than is probably needed for many Android devices.
Project Member

Comment 1 by bugdroid1@chromium.org, May 4 2016 

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

commit 9e34ffef06ca462936f1d158130cff4843e943af
Author: rtoy <rtoy@chromium.org>
Date: Wed May 04 16:16:50 2016

Add UMA for hardware buffer size and callback buffer size

Measure and report the buffer size recommended by the hardware (for
minimum latency) and the callback buffer size that is actually used.

BUG= 608510 
TEST=manually create AudioContexts and examine chrome://histograms

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

[modify] https://crrev.com/9e34ffef06ca462936f1d158130cff4843e943af/third_party/WebKit/Source/platform/audio/AudioDestination.cpp
[modify] https://crrev.com/9e34ffef06ca462936f1d158130cff4843e943af/tools/metrics/histograms/histograms.xml

Comment 2 by rtoy@chromium.org, May 5 2016

Status: Verified (was: Started)
UMA stats available; closing.
►

Sign in to add a comment