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

Issue 809038 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Feb 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.4% regression in system_health.memory_mobile at 533410:533482

Project Member Reported by mvstan...@chromium.org, Feb 5 2018

Issue description

Not a big degrade, but perhaps bisect finds something.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=809038

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


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

android-nexus5
Cc: bmeu...@chromium.org gsat...@chromium.org
Owner: bmeu...@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14bdcc21840000

[builtins] Refactor promises to reduce GC overhead. by bmeurer@chromium.org
v8 @ 8e7737cb5811dcb9bc9e125acd9d7d4e0cfcac70

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Cc: u...@chromium.org
Status: WontFix (was: Assigned)
Promises and related objects became a lot cheaper with the above mentioned change, so we run fewer GCs, which probably means that we don't compact as aggressively with the new GC timings.
Cc: s...@chromium.org torne@chromium.org agrieve@chromium.org yfried...@chromium.org pasko@chromium.org npm@chromium.org roc...@chromium.org
 Issue 808662  has been merged into this issue.
Yay! Bisect worked! :D Thx for the info Ulan..

Sign in to add a comment