New issue
Advanced search Search tips

Issue 915162 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Dec 21
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.7% regression in system_health.memory_desktop at 616164:616218

Project Member Reported by petermarshall@chromium.org, Dec 14

Issue description

Lots of regressions...
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=915162

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


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

mac-10_12_laptop_low_end-perf

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
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/1087e70a140000

Field Trial: Drop runtime flag for V8ContextSnapshot by peria@chromium.org
https://chromium.googlesource.com/chromium/src/+/523efae2ae9590d0bc4c0229277020db49fb5438
memory:chrome:all_processes:reported_by_chrome:v8:effective_size: 4.201e+07 → 4.471e+07 (+2.694e+06)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Status: Fixed (was: Assigned)
r617061 seems to have fixed this issue.

Sign in to add a comment