New issue
Advanced search Search tips

Issue 629340 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 628212
Owner:
Closed: Jul 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

10.1% regression in blink_perf.layout at 405136:405202

Project Member Reported by m...@chromium.org, Jul 19 2016

Issue description

See the link to graphs below.
 

Comment 1 by m...@chromium.org, Jul 19 2016

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiqfduQkM


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

chromium-rel-win7-gpu-ati
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 19 2016

Mergedinto: 628212
Status: Duplicate (was: Assigned)

===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Disable Full-WPO for the x64 official build (non-PGO).
Author  : sebmarchand
Commit description:
  
Disable Full-WPO for the x64 official builds (this doesn't
affect the PGO builds).

This should help me to get an official
"non-PGO & non-WPO" build that I can compare against an official PGO
build.

Also I'm not sure if it's worth keeping WPO turned on for the official
builds at the moment ? We don't ship these builds (we ship the PGO ones)
and so this only slowdown the builders that build an official x64 build
for testing purposes (especially considering that they need to link all the unittests with Full-WPO)

BUG= 490934 , 617982

Review-Url: https://codereview.chromium.org/2142603002
Cr-Commit-Position: refs/heads/master@{#405164}
Commit  : 0d74d7f71c93bfc3b32653de7958ff84d173937d
Date    : Wed Jul 13 15:42:28 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@405135  26.9572  0.0823013  5  good
chromium@405151  26.8933  0.0998358  5  good
chromium@405161  26.876   0.210692   5  good
chromium@405163  26.3228  0.869966   5  good
chromium@405164  24.2029  0.310661   5  bad    <--
chromium@405166  23.7788  0.0910365  5  bad
chromium@405171  23.7623  0.125998   5  bad
chromium@405202  24.0066  0.304404   5  bad

Bisect job ran on: winx64ati_perf_bisect
Bug ID: 629340

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.layout
Test Metric: flexbox-lots-of-data/flexbox-lots-of-data
Relative Change: 10.95%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64ati_perf_bisect/builds/1437
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006754474363416944


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5905051571191808

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

Sign in to add a comment