New issue
Advanced search Search tips

Issue 921590 link

Starred by 1 user
Status: Assigned
Owner: ----
Cc:
peter.wm...@gmail.com
petermarshall@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.5% regression in system_health.memory_desktop at 620543:620644

Project Member Reported by petermarshall@chromium.org, Jan 14 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 14 

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

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


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

Win 7 Perf

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 14

Cc: peter.wm...@gmail.com
Status: Assigned (was: Unconfirmed)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11ed4cdf940000

[js] Remove CORE JS Natives (prologue.js), port extra utils to C++/Torque by peter.wm.wong@gmail.com
https://chromium.googlesource.com/v8/v8/+/263dce9b578c0809594cc8b2b94ae9b0ba982796
memory:chrome:all_processes:reported_by_chrome:v8:effective_size: 2.115e+07 → 2.162e+07 (+4.719e+05)

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

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

Sign in to add a comment