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

Issue 768291 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

1.2%-1.6% regression in media.android.tough_video_cases_tbmv2 at 503668:503822

Project Member Reported by mlippautz@chromium.org, Sep 25 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 25 2017

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

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


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

android-nexus5X
android-nexus6
android-nexus7v2
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 25 2017

Cc: albertnetymk@google.com
Owner: albertnetymk@google.com
Status: Assigned (was: Untriaged)

=== Auto-CCing suspected CL author albertnetymk@google.com ===

Hi albertnetymk@google.com, 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 : Albert Mingkun Yang
  Commit : c9b08c6579a2a56a2a763318447788e4d1405365
  Date   : Fri Sep 22 12:28:38 2017
  Subject: Use args to avoid unnecessary work in RecordWrite stub

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : media.android.tough_video_cases_tbmv2
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/video.html?src_tulip2.mp4_busyjs
  Change       : 1.64% | 4363690.0 -> 4435236.66667

Revision                           Result                  N
chromium@503667                    4363690 +- 1358.84      6      good
chromium@503706                    4363989 +- 231.701      6      good
chromium@503726                    4363329 +- 1803.31      6      good
chromium@503736                    4363381 +- 1986.57      6      good
chromium@503741                    4363339 +- 1963.43      6      good
chromium@503743                    4363623 +- 1519.68      6      good
chromium@503744                    4363411 +- 1742.0       6      good
chromium@503744,v8@b4ff29d870      4363657 +- 1370.96      6      good
chromium@503744,v8@c9b08c6579      4434900 +- 2044.22      6      bad       <--
chromium@503745                    4435237 +- 1215.66      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.tulip2.mp4.busyjs media.android.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/8967498802312779376


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

Comment 4 by 42576172...@developer.gserviceaccount.com, Sep 25 2017

Cc: johnchen@chromium.org
 Issue 768379  has been merged into this issue.
Owner: u...@chromium.org

Comment 6 by u...@chromium.org, Sep 28 2017

Status: WontFix (was: Assigned)
The graphs recovered.

Sign in to add a comment