New issue
Advanced search Search tips

Issue 908103 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.9%-10.2% regression in system_health.common_desktop at 607136:607162

Project Member Reported by majidvp@chromium.org, Nov 23

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=908103

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


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

linux-perf
mac-10_13_laptop_high_end-perf

system_health.common_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Cc: aboxhall@chromium.org
Owner: aboxhall@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11272edfe40000

Prefer walking the LayoutTreeBuilder tree when building the Accessibility tree. by aboxhall@chromium.org
https://chromium.googlesource.com/chromium/src/+/e7316d0c2c1a3ea146197778d926502c9646e4bf
cpu_time_percentage: 0.2253 → 0.2457 (+0.02041)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
The original change has been reverted, although will probably be un-reverted at some point. 

Sign in to add a comment