New issue
Advanced search Search tips

Issue 713720 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

13.7% improvement in thread_times.key_silk_cases at 463684:463868

Project Member Reported by samans@chromium.org, Apr 20 2017

Issue description

See the link to graphs below.
 

Comment 1 by samans@chromium.org, Apr 20 2017

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

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


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

android-nexus5X
Project Member

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

Owner: samans@chromium.org

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

Hi samans@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 : samans
  Commit : 2040988b1345e6ce738bd03ab7ccd5f4b73a956b
  Date   : Tue Apr 11 23:58:35 2017
  Subject: Use MojoCompositorFrameSink in RendererCompositorFrameSink

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_IO_cpu_time_per_frame/thread_IO_cpu_time_per_frame
  Change       : 13.58% | 3.10007336871 -> 2.67918636153

Revision             Result                    N
chromium@463683      3.10007 +- 0.0715098      6      good
chromium@463776      3.13267 +- 0.0807007      6      good
chromium@463822      3.09426 +- 0.0491901      6      good
chromium@463834      3.1241 +- 0.0816668       6      good
chromium@463840      3.11985 +- 0.0766259      6      good
chromium@463843      3.10723 +- 0.1013         6      good
chromium@463844      3.11067 +- 0.0599233      6      good
chromium@463845      2.69319 +- 0.0443423      6      bad       <--
chromium@463868      2.67919 +- 0.0578677      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 thread_times.key_silk_cases

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

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


| 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 samans@chromium.org, May 29 2017

Status: WontFix (was: Untriaged)

Sign in to add a comment