New issue
Advanced search Search tips

Issue 918616 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.8%-2.6% regression in system_health.memory_desktop at 617043:617132

Project Member Reported by lanwei@chromium.org, Jan 2

Issue description

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

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


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

Win 7 Nvidia GPU Perf
Win 7 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/15b48dc2940000

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.788e+07 → 1.798e+07 (+9.079e+04)

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

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

Sign in to add a comment