New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 916713 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Dec 20
Cc:
█ chromium...@skia-public.iam.gserviceaccount.com
u...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Memory improvement in Chrome 614511 - 614584 range

Project Member Reported by u...@chromium.org, Dec 19 
Creating a bug for pinpoint bisect job.

Comment 1 by u...@chromium.org, Dec 19

Summary: Memory improvement in Chrome 614511 - 614584 range (was: Memory improvement in V8 range c5bfa5d - 2192eb7 )
Project Member

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

Cc: chromium...@skia-public.iam.gserviceaccount.com
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/115c34fa140000

Roll src/third_party/catapult d18d6c7c7183..5d7bcad36ff4 (2 commits) by chromium-autoroll@skia-public.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/ac8ebb246231cdea5872c01e6d596a00462678a3
memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size: 2.861e+06 → 5.987e+05 (-2.262e+06)

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

Benchmark documentation link:
  None

Comment 4 by u...@chromium.org, Dec 20

Cc: u...@chromium.org
Owner: ----
Status: WontFix (was: Assigned)
The improvements come from change in the benchmarking infra.
►

Sign in to add a comment