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

Issue 887957 link

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



Sign in to add a comment

1.3%-1.7% regression in system_health.memory_desktop at 592380:592522

Project Member Reported by jgruber@chromium.org, Sep 21 
Maybe return to baseline.
Project Member

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

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

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


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

Win 7 Nvidia GPU Perf

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Project Member

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

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/15403a98e40000

[interpreter] Restrict one-shot optimizations to only top-level IIFEs by chandanreddy@google.com
https://chromium.googlesource.com/v8/v8/+/b2ed47b958f43c91d0b4bc8c1bbff5d60ac45064
9.459e+06 → 9.622e+06 (+1.631e+05)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

Comment 4 by chandanreddy@google.com, Sep 24

Cc: cbruni@chromium.org
►

Sign in to add a comment