Issue metadata
Sign in to add a comment
|
Ganesh-induced Performance Regressions |
||||||||||||||||||||||
Issue descriptionThe introduction of Ganesh introduced a fairly large memory regression, e.g. https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgj5CttQoM. This has been largely alleviated by a subsequent fix that linked Ganesh to the correct GL interface, but it's still ~1MB higher than it was previously. The regression appears to be solely in the memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg measurement.
,
Nov 16 2017
It seems that the memory regression went away. However, we now see a small regression in text rendering times: https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgr96LswkM
,
Nov 21 2017
The text rendering regression seem to have gone away too.
,
Feb 2 2018
Closing since regression went away.
,
Feb 2 2018
,
Feb 8 2018
,
Feb 22 2018
,
Jul 4
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by bsheedy@chromium.org
, Nov 15 2017