New issue
Advanced search Search tips

Issue 757339 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

A zero-to-nonzero regression in media.tough_video_cases_tbmv2 at 495669:495789

Project Member Reported by liberato@google.com, Aug 21 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 21 2017

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=757339

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=36776a384614b779b0874cdf5ac01d72084f018a8a7a7cdfa6709380e6f9646e


Bot(s) for this bug's original alert(s):

chromium-rel-mac11
chromium-rel-mac12
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 21 2017

Cc: ssid@chromium.org
Owner: ssid@chromium.org
Status: Assigned (was: Untriaged)

=== Auto-CCing suspected CL author ssid@chromium.org ===

Hi ssid@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Siddhartha
  Commit : e241d0ac5772386e8b7e8016c99c0ac5d07e8dcb
  Date   : Fri Aug 18 23:11:02 2017
  Subject: Memory-infra: Remove use of unique tracing ID and add resident size to discardable dumps

Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : memory:chrome:all_processes:reported_by_chrome:discardable:effective_size_avg/memory:chrome:all_processes:reported_by_chrome:discardable:effective_size_avg

Revision             Result                  N
chromium@495705      0.0 +- 0.0              6      good
chromium@495726      0.0 +- 0.0              6      good
chromium@495729      0.0 +- 0.0              6      good
chromium@495731      0.0 +- 0.0              6      good
chromium@495732      9784.89 +- 3601.57      6      bad       <--
chromium@495737      9642.67 +- 1045.12      6      bad
chromium@495747      9699.56 +- 1415.95      6      bad
chromium@495789      10296.9 +- 2246.93      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests media.tough_video_cases_tbmv2

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8970675402578997120


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Aug 24 2017

Cc: chcunningham@chromium.org
 Issue 758330  has been merged into this issue.

Comment 5 by ssid@chromium.org, Aug 24 2017

Status: WontFix (was: Assigned)
The 10-50KB regression is expected since we now have better metrics to measure discardable memory size.
WAI.

Sign in to add a comment