New issue
Advanced search Search tips

Issue 917222 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1%-2.3% regression in system_health.memory_desktop at 617057:617132

Project Member Reported by kouhei@google.com, Dec 21

Issue description

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

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


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

Win 7 Perf
mac-10_13_laptop_high_end-perf

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Cc: ksolt@chromium.org
Owner: ksolt@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16b35c91140000

Add field trial for SequenceManager as a backend to MessageLoop. by ksolt@chromium.org
https://chromium.googlesource.com/chromium/src/+/2c3ca765b34121dd01da05a15fc6567c29a7695a
memory:chrome:all_processes:reported_by_chrome:malloc:effective_size: 1.98e+07 → 2.021e+07 (+4.086e+05)

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

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

Sign in to add a comment