Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(284)

Issue 2294333004: Include playbacks which never underflow in underflow metrics. (Closed)

Created:
4 years, 3 months ago by DaleCurtis
Modified:
4 years, 3 months ago
CC:
chromium-reviews, feature-media-reviews_chromium.org
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

Include playbacks which never underflow in underflow metrics. The histogram is only useful if we include playbacks which never reach an underflow state. BUG=641633 TEST=none Committed: https://crrev.com/821e803f24bdba8524c9e906e558fad9bf2bd174 Cr-Commit-Position: refs/heads/master@{#416007}

Patch Set 1 #

Total comments: 2
Unified diffs Side-by-side diffs Delta from patch set Stats (+9 lines, -0 lines) Patch
M media/blink/webmediaplayer_impl.cc View 1 chunk +9 lines, -0 lines 2 comments Download

Messages

Total messages: 13 (4 generated)
DaleCurtis
4 years, 3 months ago (2016-08-31 23:00:11 UTC) #2
chcunningham
lgtm
4 years, 3 months ago (2016-09-01 16:49:06 UTC) #3
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2294333004/1
4 years, 3 months ago (2016-09-01 16:51:59 UTC) #5
commit-bot: I haz the power
Committed patchset #1 (id:1)
4 years, 3 months ago (2016-09-01 18:44:31 UTC) #6
commit-bot: I haz the power
Patchset 1 (id:??) landed as https://crrev.com/821e803f24bdba8524c9e906e558fad9bf2bd174 Cr-Commit-Position: refs/heads/master@{#416007}
4 years, 3 months ago (2016-09-01 18:47:40 UTC) #8
DaleCurtis
+holte, the latest histograms are showing massive numbers of out-of-bounds reports. https://uma.googleplex.com/histograms/?endDate=latest&dayCount=1&histograms=Media.UnderflowCount%2CMedia.UnderflowDuration&fixupData=true&showMax=true&filters=channel%2Ceq%2C1%2Cisofficial%2Ceq%2CTrue&implicitFilters=isofficial I just noticed ...
4 years, 3 months ago (2016-09-06 21:23:59 UTC) #10
chromium-reviews
Counts for the value 0 will get counted in the underflow bucket (in your case ...
4 years, 3 months ago (2016-09-07 00:24:07 UTC) #11
Steven Holte
https://codereview.chromium.org/2294333004/diff/1/media/blink/webmediaplayer_impl.cc File media/blink/webmediaplayer_impl.cc (right): https://codereview.chromium.org/2294333004/diff/1/media/blink/webmediaplayer_impl.cc#newcode1092 media/blink/webmediaplayer_impl.cc:1092: UMA_HISTOGRAM_COUNTS_100("Media.UnderflowCount", 0); You should probably consolidate the macro calls ...
4 years, 3 months ago (2016-09-07 00:24:27 UTC) #12
Steven Holte
4 years, 3 months ago (2016-09-07 00:38:21 UTC) #13
Message was sent while issue was closed.
On 2016/09/07 00:24:27, Steven Holte wrote:
>
https://codereview.chromium.org/2294333004/diff/1/media/blink/webmediaplayer_...
> File media/blink/webmediaplayer_impl.cc (right):
> 
>
https://codereview.chromium.org/2294333004/diff/1/media/blink/webmediaplayer_...
> media/blink/webmediaplayer_impl.cc:1092:
> UMA_HISTOGRAM_COUNTS_100("Media.UnderflowCount", 0);
> You should probably consolidate the macro calls for these histograms into a
> single location, using a helper function, since each call will create a local
> static variable.
> 
>
https://codereview.chromium.org/2294333004/diff/1/media/blink/webmediaplayer_...
> media/blink/webmediaplayer_impl.cc:1131:
> UMA_HISTOGRAM_COUNTS_100("Media.UnderflowCount", ++underflow_count_);
> Generally not a good idea to have side-effecting like ++x in a macro call.  It
> should behave correctly in this case, since there is only 1 reference to this
> argument, but would be a good thing to fix.

Actually, the fact that you are recording every time you increment this counter
is probably the reason why you are seeing such extreme numbers of counts in the
overflow bucket.  If a user encounters 1000 overflows, they'll record a count of
1 in each of [0,1) - [25,26), a count of 2 in each of [26,28) - [40,42), and so
on to 5 in [95,100), and then 900 counts in the overflow bucket.  So when you
look at total counts across users, this results in massive counts in the
overflow bucket.  If you want a count of how many playback reach some threshold,
you only want to count the final number.

Powered by Google App Engine
This is Rietveld 408576698