Issue metadata
Sign in to add a comment
|
5.7%-316% regression in system_health.memory_desktop at 548944:549053 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 9 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12836cd4c40000
,
Apr 9 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14a777acc40000
,
Apr 10 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14828a8cc40000
,
Apr 10 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1488b2ccc40000
,
Apr 11 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/14a777acc40000 [objects] Merge SFI outer_scope_info and feedback_metadata by leszeks@chromium.org https://chromium.googlesource.com/v8/v8/+/6bd1d3c28015b31d33f082e019c8d3cccc22be0a Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Apr 11 2018
This should have been an unconditional improvement :/ Could it be a GC pressure thing? That's basically my excuse for any hard-to-understand regressions.
,
Apr 11 2018
The system health regression is also surprising - because this one is measuring live memory. I guess you need to reproduce.
,
Apr 19 2018
Yeah, looks like bad luck with GC timings, I see fewer GCs in general in the trace after. To be expected with an object size decrease I think.
,
May 1 2018
Issue 827994 has been merged into this issue. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Apr 9 2018