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

Issue 621803 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
please use my google.com address
Closed: Jun 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.6% regression in thread_times.simple_mobile_sites at 400030:400065

Project Member Reported by toyoshim@chromium.org, Jun 21 2016

Issue description

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

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


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

android-galaxy-s5
Project Member

Comment 2 by 42576172...@developer.gserviceaccount.com, Jun 21 2016


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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N   Good?
chromium@400029  4.47221  0.0296019  18  good
chromium@400065  4.48357  0.0409238  18  bad

Bisect job ran on: android_s5_perf_bisect
Bug ID: 621803

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.simple_mobile_sites
Test Metric: thread_IO_cpu_time_per_frame/thread_IO_cpu_time_per_frame
Relative Change: 0.84%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/727
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9009265962536450736


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

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 21 2016

Cc: roc...@chromium.org
Owner: roc...@chromium.org

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

Hi rockot@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 : Revert "Send input event IPCs directly from the UI thread"
Author  : rockot
Commit description:
  
This reverts commit 868f89e764ab0e807adb237f0cbaf79ca5f49257.
See https://codereview.chromium.org/1991323002 for the original
CL.

Per offline discussions: there was no clear benefit from
using SendNow for input events, and having the extra interface
adds unnecessary complexity given that nobody is going to work
on porting Send call sites.

BUG= 612944 
R=jam@chromium.org

Review-Url: https://codereview.chromium.org/2068343003
Cr-Commit-Position: refs/heads/master@{#400227}
Commit  : f14a8ae8f52b814820b29752996c5cee903a8d4d
Date    : Thu Jun 16 19:30:22 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev     N  Good?
chromium@399544  4.36223  0.106451    5  good
chromium@399886  4.48111  0.00951618  5  good
chromium@400057  4.52717  0.0371753   5  good
chromium@400142  4.54843  0.0207563   5  good
chromium@400185  4.52734  0.0161809   5  good
chromium@400206  4.53735  0.032758    8  good
chromium@400217  4.54678  0.0594961   8  good
chromium@400222  4.52863  0.0542443   8  good
chromium@400225  4.54072  0.0838837   8  good
chromium@400226  4.50345  0.0291675   5  good
chromium@400227  4.6866   0.0315838   8  bad    <--

Bisect job ran on: android_s5_perf_bisect
Bug ID: 621803

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.simple_mobile_sites
Test Metric: thread_IO_cpu_time_per_frame/thread_IO_cpu_time_per_frame
Relative Change: 7.22%
Score: 99.8

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/728
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9009265930191277360


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

| 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 roc...@chromium.org, Jun 21 2016

Status: WontFix (was: Assigned)
This should be expected.

Sign in to add a comment