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

Issue 777860 link

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



Sign in to add a comment

47.3% regression in system_health.common_desktop at 510669:510723

Project Member Reported by kraynov@chromium.org, Oct 24 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 24 2017 

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

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


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

chromium-rel-win7-gpu-intel
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 24 2017 


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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : cpu_time_percentage_avg/load_news/load_news_hackernews

Revision             Result                       N
chromium@510668      0.0229943 +- 0.0124263       21      good
chromium@510723      0.0225987 +- 0.00750391      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=load.news.hackernews system_health.common_desktop

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

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


For feedback, file a bug with component Speed>Bisection

Comment 5 by benhenry@chromium.org, Oct 26 2017 

Widened range.
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Oct 26 2017 


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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : cpu_time_percentage_avg/load_media/load_media_dailymotion

Revision             Result                     N
chromium@510612      0.116407 +- 0.0221928      21      good
chromium@510723      0.112654 +- 0.0527204      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=load.media.dailymotion system_health.common_desktop

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

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


For feedback, file a bug with component Speed>Bisection

Comment 7 by benhenry@chromium.org, Oct 30 2017

Status: WontFix (was: Untriaged)
std.dev is within noise of mean...is this really a regression?
►

Sign in to add a comment