Issue metadata
Sign in to add a comment
|
6.9% regression in system_health.memory_mobile at 536307:536360 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 21 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16a27ec7840000
,
Feb 23 2018
📍 Found significant differences after each of 2 commits. https://chromeperf.appspot.com/job/16a27ec7840000 [builtins] Refactor the promise resolution and rejection logic. by bmeurer@chromium.org https://chromium.googlesource.com/v8/v8/+/c0412961892cddb0455fd7eb2ea9bcd46deae15d [builtins] Optimize PromiseResolveThenableJob for the common case. by bmeurer@chromium.org https://chromium.googlesource.com/v8/v8/+/1f8dcc5d2eba108dbfaa51c7e544f3899b5cf9a0 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Feb 26 2018
Graph recovered. Looks like some infra hickup.
,
Feb 26 2018
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Feb 21 2018