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

Issue 766619 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

33.1% improvement in smoothness.top_25_smooth at 502501:502505

Project Member Reported by alexclarke@chromium.org, Sep 19 2017 
Suspiciously large improvement, could this be a bug?
Project Member

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

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

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


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

chromium-rel-win10
Project Member

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


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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : mean_input_event_latency/https___plus.google.com_110031535020051778989_posts

Revision             Result                  N
chromium@502500      13.1027 +- 4.97914      21      good
chromium@502505      13.057 +- 4.81163       21      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=https...plus.google.com.110031535020051778989.posts smoothness.top_25_smooth

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

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


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

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


=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : mean_input_event_latency/https___plus.google.com_110031535020051778989_posts

Revision             Result                  N
chromium@502505      13.3369 +- 7.88462      21      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=https...plus.google.com.110031535020051778989.posts smoothness.top_25_smooth

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

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


For feedback, file a bug with component Speed>Bisection

Comment 6 by alexclarke@chromium.org, Sep 19 2017

Status: WontFix (was: Untriaged)
Strange, the bots are not finding anything.
►

Sign in to add a comment