New issue
Advanced search Search tips

Issue 892162 link

Starred by 1 user
Status: Duplicate
Merged: issue 890413
Owner: ----
Closed: Oct 4
Cc:
chiniforooshan@chromium.org
paulmiller@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.6% regression in rendering.mobile/thread_total_all_cpu_time_per_frame at 592894:592936

Project Member Reported by chiniforooshan@chromium.org, Oct 4 
See the link to graphs below.
Project Member

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

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

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


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

Android Nexus6 WebView Perf

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

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

Cc: paulmiller@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/15af7938e40000

WebView: Configure entropy providers by paulmiller@google.com
https://chromium.googlesource.com/chromium/src/+/6bd4db44ab539859b70c348782ef3b0922ae2656
thread_total_all_cpu_time_per_frame: 25.93 → 27.52 (+1.598)

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

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

Comment 4 by paulmiller@chromium.org, Oct 4

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

Sign in to add a comment