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

Issue 636720 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Aug 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Migrate media.* Telemetry benchmarks to timeline based measurements (TBM)

Project Member Reported by perezju@chromium.org, Aug 11 2016

Issue description

Media benchmarks [1] are currently written in the old style (using memory.memory_stats). Memory metrics in the old style are being deprecated, so these need to be migrate to TBM [2].

[1]: https://cs.chromium.org/chromium/src/tools/perf/benchmarks/media.py
[2]: https://www.chromium.org/developers/telemetry/add_a_measurement#TOC-How-about-Timeline-Based-Measurement-

Not sure if there was already a bug to track this, please do close as duplicate if that's the case.
 
Blocking: 632021
Cc: rnep...@chromium.org
+rnephew who is also working on some new media benchmarks
Working on a document for it here:
https://docs.google.com/a/google.com/document/d/1hNVcM-DLvLtx87Ye659MaqPQxfIFwZ6VsjhJIShAQPY/edit?usp=sharing

Still hasn't been sent out for a wider review, but will be doing so soon.
Caleb,

We'll want the media.* Telemetry benchmarks even after we have the system health media benchmarks listed in Randy's doc, right? Just want to make sure that we keep the two separate if they need to be.
Yes, we definitely need media.* benchmarks, and the system health benchmarks won't do the job. There is a comment thread on this doc: https://docs.google.com/document/d/1AJ4GvwauT3LNHtEDEvai5DcXNzdX-ANziI3Mu6_Nvrk/edit#heading=h.yua7f2r5h3j0 explaining why. 

See https://bugs.chromium.org/p/chromium/issues/detail?id=626073#c2 for details.


Mergedinto: 626073
Status: Duplicate (was: Assigned)
Blocking: -632021

Sign in to add a comment