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

Issue 762273 link

Starred by 1 user
Status: Duplicate
Merged: issue 762247
Owner:
bcwh...@chromium.org
Closed: Sep 2017
Cc:
bcwh...@chromium.org
█ briander...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

24.7% regression in speedometer at 499150:499230

Project Member Reported by briander...@chromium.org, Sep 5 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 5 2017 

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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=c7cd54d18e82a76c5c4947372e856fa119dc2180fee3a00e194e2e9b4eb38b27


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

android-webview-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 6 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : speedometer
  Metric       : Total/Total

Revision             Result                  N
chromium@499149      32695.2 +- 748.724      21      good
chromium@499230      32734.1 +- 661.968      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests speedometer

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8969252871613079568


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Sep 7 2017

Cc: bcwh...@chromium.org
Owner: bcwh...@chromium.org
Status: Assigned (was: Untriaged)

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

Hi bcwhite@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 : Brian White
  Commit : 003796b6cd67a5ec5d1dd12577f811719cf4122d
  Date   : Sat Sep 02 18:31:07 2017
  Subject: Do histogram validation after every JNI call.

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : speedometer
  Metric       : Total/Total
  Change       : 0.33% | 33137.1876984 -> 33245.5525

Revision             Result                  N
chromium@498451      33137.2 +- 769.525      21      good
chromium@498929      33001.2 +- 618.223      9       good
chromium@499168      33042.5 +- 659.378      14      good
chromium@499287      33034.0 +- 215.194      6       good
chromium@499347      32997.8 +- 290.526      6       good
chromium@499377      32974.8 +- 153.955      6       good
chromium@499392      33014.8 +- 303.196      6       good
chromium@499399      32824.4 +- 250.878      6       good
chromium@499400      33258.1 +- 268.271      6       bad       <--
chromium@499401      33292.8 +- 203.38       6       bad
chromium@499403      33267.7 +- 432.263      6       bad
chromium@499406      33245.6 +- 363.667      14      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests speedometer

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8969171011780683152


For feedback, file a bug with component Speed>Bisection

Comment 6 by bcwh...@chromium.org, Sep 7 2017

Mergedinto: 762247
Status: Duplicate (was: Assigned)
►

Sign in to add a comment