New issue
Advanced search Search tips

Issue 897144 link

Starred by 1 user
Status: Assigned
Owner:
tommycli@chromium.org
Cc:
tommycli@chromium.org
hjd@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.2% regression in rendering.mobile/thread_total_all_cpu_time_per_frame at 600487:600567

Project Member Reported by hjd@google.com, Oct 19 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 19 

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

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


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

Android Nexus5 Perf

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 22

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

Omnibox: Steady State Elisions - Add a trim everything but origin flag by tommycli@chromium.org
https://chromium.googlesource.com/chromium/src/+/bef94ee00fcb2b8a94fbd9b0323094fbc37e9601
thread_total_all_cpu_time_per_frame: 109 → 110.4 (+1.382)

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

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

Sign in to add a comment