Issue metadata
Sign in to add a comment
|
1.8%-3.8% regression in memory.top_10_mobile at 533410:533482 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 2 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/11d08abe840000
,
Feb 3 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/11d08abe840000 Move initCommandLine() to attachBaseContext (take 2) by agrieve@chromium.org chromium @ 7ee6c14b661b0abdfb91f8f0c8a07c34f1d353bc Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Feb 5 2018
Regression seems legitimate, but I don't see how my change could affect memory. Going to ask for another bisect.
,
Feb 5 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14ea4ce1840000
,
Feb 6 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/14ea4ce1840000 [builtins] Refactor promises to reduce GC overhead. by bmeurer@chromium.org v8 @ 8e7737cb5811dcb9bc9e125acd9d7d4e0cfcac70 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Feb 6 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Feb 2 2018