Issue metadata
Sign in to add a comment
|
1.1%-1.9% regression in jetstream at 522212:522379 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 14 2017
๐ Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/13a95132040000
,
Dec 15 2017
๐ Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/13a95132040000 Enable --write-protect-code-memory by default. By mstarzinger@chromium.org ยท Wed Dec 06 10:14:58 2017 v8 @ 02d201bfdd18f1292146dd32bcca911c3465a991 [heap] Add tracing scope for concurrent marking. By ulan@chromium.org ยท Wed Dec 06 10:33:48 2017 v8 @ fc5b2ff106d95b13e9575332692d0927f04b6fef Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Dec 15 2017
Regression from my CL is unexpected. It adds tiny overhead to concurrent marker. mstarzinger@, could it be related to SunSpider regression from W^X?
,
Dec 15 2017
Assigning to Michael after offline discussion.
,
Dec 15 2017
,
Jan 23 2018
Michael: perf sheriff checking in, any progress on this bug?
,
Aug 17
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Dec 14 2017