New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 890884 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Oct 17
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.8% regression in rendering.mobile/thread_total_all_cpu_time_per_frame at 594279:594310

Project Member Reported by tdres...@chromium.org, Oct 1

Issue description

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

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


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

Android Nexus5X WebView Perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Cc: chandanreddy@google.com neis@chromium.org
Owner: chandanreddy@google.com
Status: Assigned (was: Untriaged)
📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/14d8aed8e40000

[turbofan] Remove redundant isolate argument from typers. by neis@chromium.org
https://chromium.googlesource.com/v8/v8/+/74b40e34d56946e450fa96673357f5a593dc5683
23.87 → 23.46 (-0.4064)

[interpreter] Separate bytecodes for one-shot property loads and stores by chandanreddy@google.com
https://chromium.googlesource.com/v8/v8/+/eccf18674911a3d8a84213589e4bda70bf81aeb1
23.52 → 24.54 (+1.016)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Cc: cbruni@chromium.org
Looks like One-shot CL is not the cause of regression
https://pinpoint-dot-chromeperf.appspot.com/job/165ed9e4e40000
Status: WontFix (was: Assigned)

Sign in to add a comment