New issue
Advanced search Search tips

Issue 876554 link

Starred by 1 user
Status: Duplicate
Owner:
alexilin@chromium.org
Closed: Aug 28
Cc:
alexilin@chromium.org
hjd@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.1% regression in system_health.memory_mobile at 584108:584164

Project Member Reported by hjd@google.com, Aug 21 
See the link to graphs below.
Project Member

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

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

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


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

android-nexus5x-perf
Project Member

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

Cc: alexilin@chromium.org
Owner: alexilin@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12eb6506640000

predictors: Use NetworkContext's APIs to preconnect sockets and resolve hosts. by alexilin@chromium.org
https://chromium.googlesource.com/chromium/src/+/5b417db655388d726c0724f5a12425a5ddd68904
4.029e+07 → 4.116e+07 (+8.677e+05)

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

Comment 4 by hjd@chromium.org, Aug 28

Mergedinto: 877270
Status: Duplicate (was: Assigned)
►

Sign in to add a comment