New issue
Advanced search Search tips

Issue 911963 link

Starred by 1 user
Status: Assigned
Owner:
chiniforooshan@chromium.org
Cc:
chiniforooshan@chromium.org
toyoshim@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

A zero-to-nonzero to 7.2% regression in rendering.desktop/tasks_per_frame_total_all at 603864:606971

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

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

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

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


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

Win 7 Nvidia GPU Perf
Win 7 Perf

rendering.desktop - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 6

Cc: chiniforooshan@chromium.org
Owner: chiniforooshan@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14a06c74140000

Telemetry: remove old cpu_per_frame metrics by chiniforooshan@chromium.org
https://chromium.googlesource.com/chromium/src/+/af5198be3516b3e7e5f54e9cdf6dc2882e1e4100
thread_total_all_cpu_time_per_frame: 1.903 → 16.9 (+15)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
►

Sign in to add a comment