New issue
Advanced search Search tips

Issue 815088 link

Starred by 1 user
Status: Duplicate
Merged: issue 813745
Owner:
verwa...@chromium.org
Closed: Feb 2018
Cc:
jgruber@chromium.org
verwa...@chromium.org
ishell@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.2% regression in v8.browsing_desktop at 537176:537310

Project Member Reported by jgruber@chromium.org, Feb 23 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Feb 23 2018 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=815088

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


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

linux-release
Project Member

Comment 2 by 42576172...@developer.gserviceaccount.com, Feb 23 2018 

📍 Pinpoint job started.
https://chromeperf.appspot.com/job/168242df840000
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Feb 23 2018

Cc: ishell@chromium.org verwa...@chromium.org
Owner: verwa...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://chromeperf.appspot.com/job/168242df840000

[json] Always internalize json string values to avoid memory overhead by verwaest@chromium.org
https://chromium.googlesource.com/v8/v8/+/2a5791ce2d0d71e99e7fa2065470b44b90f3e6a5

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

Comment 4 by ishell@chromium.org, Feb 23 2018

Mergedinto: 813745
Status: Duplicate (was: Assigned)
See  issue 813745 , #c4
►

Sign in to add a comment