New issue
Advanced search Search tips

Issue 635464 link

Starred by 1 user
Status: WontFix
Owner:
erikc...@chromium.org
Closed: Aug 2016
Cc:
erikc...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.5%-10.9% regression in startup.warm.blank_page at 410128:410190

Project Member Reported by rmcilroy@chromium.org, Aug 8 2016 
See the link to graphs below.
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 8 2016 


===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@410161  12.7108  0.250778   5  good
chromium@410162  12.8086  0.219714   5  good
chromium@410163  14.208   0.0810802  5  bad
chromium@410165  14.1792  0.0622792  5  bad
chromium@410169  14.1264  0.148434   5  bad
chromium@410177  14.0956  0.074137   5  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 635464

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: mean_input_event_latency/Wikipedia (1 tab)
Relative Change: 10.89%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2278
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004901969138185664


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

| 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!

Comment 4 by sullivan@chromium.org, Aug 8 2016

Owner: erikc...@chromium.org
erikchen: Looks like the bisect showed a jump in startup with https://codereview.chromium.org/2215513002

(The confusing output is tracked in https://github.com/catapult-project/catapult/issues/2626)
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Aug 8 2016 


===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@410161  12.7108  0.250778   5  good
chromium@410162  12.8086  0.219714   5  good
chromium@410163  14.208   0.0810802  5  bad
chromium@410165  14.1792  0.0622792  5  bad
chromium@410169  14.1264  0.148434   5  bad
chromium@410177  14.0956  0.074137   5  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 635464

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: mean_input_event_latency/Wikipedia (1 tab)
Relative Change: 10.89%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2278
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004901969138185664


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

| 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!

Comment 8 by erikc...@chromium.org, Aug 9 2016

Status: WontFix (was: Assigned)
The relevant CL has been reverted.
Project Member

Comment 10 by 42576172...@developer.gserviceaccount.com, Aug 9 2016

Cc: erikc...@chromium.org

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

Hi erikchen@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : Reland #1: "base: Implement GetCurrentThreadPriority."
Author  : erikchen
Commit description:
  
The Chrome thread priority is saved in the thread dictionary during
SetCurrentThreadPriority(). This seemed a better approach than using
thread_policy_get(), since there are 4 Chrome priorities which won't cleanly map
to thread flavors.

BUG=601270

Review-Url: https://codereview.chromium.org/2215513002
Cr-Commit-Position: refs/heads/master@{#410163}
Commit  : 23d10a36f2e815edd610098a65e5890f279d2183
Date    : Fri Aug 05 21:19:08 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@410161  12.6846  0.36589    5  good
chromium@410162  12.6546  0.218651   5  good
chromium@410163  14.0016  0.233697   5  bad    <--
chromium@410165  14.0874  0.0346165  5  bad
chromium@410169  14.0034  0.19797    5  bad
chromium@410177  14.0664  0.189091   5  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 635464

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: mean_input_event_latency/Wikipedia (1 tab)
Relative Change: 10.89%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2287
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004901969138185664


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

| 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