New issue
Advanced search Search tips

Issue 911981 link

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



Sign in to add a comment

13.4%-30.1% regression in rendering.desktop/frame_times at 612610:612801

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=911981

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


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 5

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

Revert "Perfetto: Stop splitting _COMPLETE events" by oysteine@chromium.org
https://chromium.googlesource.com/chromium/src/+/6a796b426b1ff987c8e4fd63d838731bcfd50d54
thread_raster_cpu_time_per_frame: 0.01335 → 0.01723 (+0.003879)

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

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

Sign in to add a comment