New issue
Advanced search Search tips

Issue 893865 link

Starred by 1 user
Status: Duplicate
Merged: issue 893820
Owner:
jarin@chromium.org
Closed: Oct 10
Cc:
m...@chromium.org
jarin@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

10.4%-69.9% regression in rendering.mobile/thread_total_all_cpu_time_per_frame at 597203:597277

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

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

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

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


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

Android Nexus5X WebView Perf
Android Nexus6 WebView Perf

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

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

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

[turbofan] Only poison loads and branches participating in property access by jarin@chromium.org
https://chromium.googlesource.com/v8/v8/+/fe7577027613eb901d8e87805dfe02aef45ae572
queueing_durations: 1.652 → 2.573 (+0.9212)

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

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

Comment 4 by m...@chromium.org, Oct 10

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

Sign in to add a comment