New issue
Advanced search Search tips

Issue 917093 link

Starred by 2 users
Status: Duplicate
Owner:
peria@chromium.org
Closed: Jan 8
Cc:
mlippautz@chromium.org
peria@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.2%-8.3% regression in system_health.memory_desktop at 617030:617078

Project Member Reported by mlippautz@chromium.org, Dec 20 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 20 

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

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


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

Win 7 Nvidia GPU Perf
Win 7 Perf
linux-perf
mac-10_13_laptop_high_end-perf

memory.desktop - Benchmark documentation link:
  None

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 21

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

binding: Drop a runtime enabled flag for V8ContextSnapshot by peria@chromium.org
https://chromium.googlesource.com/chromium/src/+/ff19f4443204410b3be71c476d23c716db18c800
memory:chrome:all_processes:reported_by_chrome:v8:effective_size: 6.324e+06 → 6.849e+06 (+5.243e+05)

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

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

Comment 4 by peria@chromium.org, Jan 8

Mergedinto: 909788
Status: Duplicate (was: Assigned)

Comment 5 by peria@chromium.org, Jan 8

Mergedinto: -909788 916443
►

Sign in to add a comment