New issue
Advanced search Search tips

Issue 876739 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Aug 23
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.3%-2.5% regression in system_health.memory_desktop at 584759:584788

Project Member Reported by cbruni@google.com, Aug 22

Issue description

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

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


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

mac-10_13_laptop_high_end-perf
Cc: verwa...@chromium.org
Owner: verwa...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11eb6506640000

[scanner] Go back to untemplatized scanning with buffering by verwaest@chromium.org
https://chromium.googlesource.com/v8/v8/+/fcfd995aa1ce3095dd3b8e34aa2c9b34b3d47f1d
1.914e+08 → 1.955e+08 (+4.135e+06)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: WontFix (was: Assigned)
That CL is a revert.

Sign in to add a comment