New issue
Advanced search Search tips

Issue 889787 link

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



Sign in to add a comment

2.7%-6.3% regression in speedometer2 at 592336:592522

Project Member Reported by bmeurer@google.com, Sep 27 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 27 

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

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


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

Win 7 Nvidia GPU Perf
Win 7 Perf

speedometer2 - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 27

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/11c9b18f640000

Turn on full masking with untrusted-code-mitigations by jarin@chromium.org
https://chromium.googlesource.com/v8/v8/+/6a6f050e18b90d5b498d85455e598ca68b14238f
499.1 → 528.1 (+29)

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

Benchmark documentation link:
  None

Comment 5 by jarin@chromium.org, Oct 5

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

Sign in to add a comment