New issue
Advanced search Search tips

Issue 773706 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

12.9% regression in smoothness.gpu_rasterization.tough_filters_cases at 506705:506779

Project Member Reported by nzolghadr@chromium.org, Oct 11 2017

Issue description

See the link to graphs below.
 
Project Member

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

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

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


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

chromium-rel-win7-gpu-nvidia
Project Member

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


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

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.tough_filters_cases
  Metric       : frame_times/Analog Clock SVG

Revision             Result                  N
chromium@506704      22.8511 +- 16.8117      21      good
chromium@506779      23.0676 +- 6.66874      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=Analog.Clock.SVG smoothness.gpu_rasterization.tough_filters_cases

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

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


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

Comment 5 by 42576172...@developer.gserviceaccount.com, Oct 21 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_nexus6_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_renderer_compositor_cpu_time_per_frame/http___www.ebay.co.uk_

Revision             Result                    N
chromium@506414      2.66281 +- 0.0540464      6        good
chromium@506563      2.6591 +- 0.0799112       14       good
chromium@506575      2.65321 +- 0.143579       21       good
chromium@506576      ---                       ---      build failure
---                  ---                       ---      too many build failures to list
chromium@506592      2.67193 +- 0.142387       21       unknown
chromium@506595      2.68162 +- 0.143607       21       bad
chromium@506601      2.68431 +- 0.10295        14       bad
chromium@506638      2.7295 +- 0.0936568       6        bad
chromium@506712      2.79248 +- 0.0667288      6        bad

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...www.ebay.co.uk. thread_times.simple_mobile_sites

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

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


For feedback, file a bug with component Speed>Bisection
Status: WontFix (was: Untriaged)
This recovered.

Sign in to add a comment