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

Issue 887305 link

Starred by 1 user
Status: Assigned
Owner:
█ chandanreddy@google.com
Last visit > 30 days ago
Cc:
█ chandanreddy@google.com
█ alexclarke@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

26.2% regression in octane at 591755:591915

Project Member Reported by alexclarke@chromium.org, Sep 20 
See the link to graphs below.
Project Member

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

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

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


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

Win 7 Perf

octane - Benchmark documentation link:
  None
Project Member

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

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

[Interpreter] Create and use CallNoFeedback bytecode for one-shot code by chandanreddy@google.com
https://chromium.googlesource.com/v8/v8/+/aaab2907cc1fffec6351b03d22084ebe74bdae62
1.614e+04 → 1.18e+04 (-4339)

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

Benchmark documentation link:
  None
►

Sign in to add a comment