New issue
Advanced search Search tips

Issue 896344 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 899002
Owner:
Closed: Oct 25
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocking:
issue 898270



Sign in to add a comment

1% regression in system_health.memory_desktop at 599611:599654

Project Member Reported by sullivan@chromium.org, Oct 17

Issue description

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

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


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

Win 7 Perf

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/15de9dcae40000
Bisecting on a wider range.
Cc: backer@chromium.org
Owner: backer@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/142daa46e40000

Use RasterDecoder for CPU raster by backer@chromium.org
https://chromium.googlesource.com/chromium/src/+/8e4f35d1fe31c1b0b8f0123a10d498f0139b9097
memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size: 4.008e+08 → 4.05e+08 (+4.252e+06)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Blocking: 898270
Labels: vulkanize
Mergedinto: 899002
Status: Duplicate (was: Assigned)

Sign in to add a comment