New issue
Advanced search Search tips

Issue 711297 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

42.4% regression in page_cycler_v2.intl_ja_zh at 463217:463286

Project Member Reported by primiano@chromium.org, Apr 13 2017

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=711297

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


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

chromium-rel-win7-gpu-nvidia
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Apr 13 2017

Cc: jochen@chromium.org
Owner: jochen@chromium.org

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

Hi jochen@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 : jochen
  Commit : b4c4f2c525c4bc3e1494291cb8b83ebbb298c050
  Date   : Mon Apr 10 14:48:41 2017
  Subject: Explicitly tell the preload request where to take the referrer from

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : page_cycler_v2.intl_ja_zh
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___ruten.com.tw_
  Change       : 57.10% | 348.106111113 -> 546.88

Revision             Result                  N
chromium@463216      348.106 +- 1.30707      9       good
chromium@463251      349.295 +- 9.90824      6       good
chromium@463260      348.636 +- 2.50653      9       good
chromium@463263      349.308 +- 6.34047      14      good
chromium@463264      504.122 +- 678.179      21      bad       <--
chromium@463265      581.443 +- 456.076      14      bad
chromium@463269      547.498 +- 415.692      9       bad
chromium@463286      546.88 +- 420.136       9       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...ruten.com.tw. page_cycler_v2.intl_ja_zh

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982422102981261920

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5896044405063680


| 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 Speed>Bisection.  Thank you!

Comment 4 by jochen@chromium.org, Apr 13 2017

Status: WontFix (was: Untriaged)
I broke the test in https://codereview.chromium.org/2780533002 and this is the fix that brings the test back to normal
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Apr 13 2017

 Issue 711296  has been merged into this issue.

Sign in to add a comment