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

Issue 792055 link

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



Sign in to add a comment

7.3% regression in thread_times.key_mobile_sites_smooth at 519999:520047

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

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

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

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


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

android-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 5 2017 


=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.key_mobile_sites_smooth
  Metric       : thread_renderer_compositor_cpu_time_per_frame/http___nytimes.com_


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 --story-filter=http...nytimes.com. thread_times.key_mobile_sites_smooth

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

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


For feedback, file a bug with component Speed>Bisection

Comment 5 by pmeenan@chromium.org, Dec 5 2017 

Kicked off a new bisect.  Ref build looks like it stopped testing so hard to see if it is a real regression.
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Dec 5 2017 


=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.key_mobile_sites_smooth
  Metric       : thread_renderer_compositor_cpu_time_per_frame/thread_renderer_compositor_cpu_time_per_frame


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 --story-filter=http...nytimes.com. thread_times.key_mobile_sites_smooth

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

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


For feedback, file a bug with component Speed>Bisection

Comment 7 by pmeenan@chromium.org, Dec 5 2017

Status: WontFix (was: Untriaged)
►

Sign in to add a comment