New issue
Advanced search Search tips

Issue 909809 link

Starred by 1 user
Status: Duplicate
Owner:
oysteine@chromium.org
Closed: Nov 29
Cc:
oysteine@chromium.org
majidvp@chromium.org
style-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

38.3% regression in blink_perf.css at 603928:604050

Project Member Reported by majidvp@google.com, Nov 28 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 28 

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

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


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

Win 7 Nvidia GPU Perf

blink_perf.css - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 29

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/1451bd6be40000

Reland "Enable Perfetto by default for all telemetry tests" by oysteine@chromium.org
https://chromium.googlesource.com/chromium/src/+/3bb24369bef996b43b2d2711f0033ba472f779ea
ChangeStyleShallowTree: 60.86 → 83.95 (+23.09)

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

Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

Comment 4 by oysteine@chromium.org, Nov 29

Mergedinto: 902480
Status: Duplicate (was: Assigned)
►

Sign in to add a comment