Issue metadata
Sign in to add a comment
|
1.1%-3.1% regression in system_health.memory_desktop at 522382:522413 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 8 2017
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/129afa02040000
,
Jan 22 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/168d6298840000
,
Jan 22 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14e7a4b8840000
,
Jan 22 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16ca04d8840000
,
Jan 22 2018
Re-kicked bisect.
,
Feb 2 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12bfd0de840000
,
Feb 2 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/12bfd0de840000 [x64] Reduce deoptimization table size by kanghua.yu@intel.com v8 @ 12276adf8ac482158c1fd606c5f90b9af9450bba Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Mar 16 2018
Assigning to reviewer mstarzinger since kanghua.yu@intel.com didn't respond and doesn't have editbugs, can you help triage this memory regression?
,
Aug 2
,
Aug 2
|
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Dec 8 2017