Issue metadata
Sign in to add a comment
|
1% regression in system_health.memory_mobile at 537200:537249 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 20 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/158374fb840000
,
Feb 20 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/158374fb840000 [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
,
Feb 20 2018
There are many more improvements related to the CL than regressions, see https://chromeperf.appspot.com/group_report?rev=537249
,
Feb 20 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14ac9c17840000
,
Feb 22 2018
📍 Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/14ac9c17840000 [json] Always internalize json string values to avoid memory overhead by verwaest@chromium.org https://chromium.googlesource.com/v8/v8/+/2a5791ce2d0d71e99e7fa2065470b44b90f3e6a5 Reland "[ic] EmitElementStore: don't miss when hitting new space limit." by neis@chromium.org https://chromium.googlesource.com/v8/v8/+/a50bc8ac8dc018f253a702bf742b9861111c0b3d Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Feb 22 2018
,
Feb 23 2018
Issue 815088 has been merged into this issue. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Feb 20 2018