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

Issue 783702 link

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



Sign in to add a comment

5.5% regression in thread_times.tough_compositor_cases at 514432:514476

Project Member Reported by alexclarke@chromium.org, Nov 10 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 10 2017 

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

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


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

win-high-dpi
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 10 2017 


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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : thread_times.tough_compositor_cases
  Metric       : tasks_per_frame_other/tasks_per_frame_other

Revision             Result                     N
chromium@514431      0.296838 +- 0.0271077      21      good
chromium@514476      0.294867 +- 0.0266212      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 thread_times.tough_compositor_cases

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

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


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

Comment 5 by 42576172...@developer.gserviceaccount.com, Nov 13 2017 


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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : thread_times.tough_compositor_cases
  Metric       : tasks_per_frame_other/tasks_per_frame_other

Revision             Result                     N
chromium@514431      0.299069 +- 0.03614        21      good
chromium@514476      0.295386 +- 0.0229472      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 thread_times.tough_compositor_cases

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

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


For feedback, file a bug with component Speed>Bisection

Comment 6 by sullivan@chromium.org, Jan 12 2018

Status: WontFix (was: Untriaged)
Bisect can't repro, and this seems like a return to previous levels. Seems like  fluke?
►

Sign in to add a comment