Meta: performance regressions caused by switching site-per-process to be the default |
|||||||||||||||||
Issue descriptionIssue 824966 tracked making --site-per-process the default for //chrome layer on ToT. This happened on 2018-04-21 in r552589. Let's use this bug as a meta-bug to track various performance regressions that were detected after site-per-process became the default. ⛆ |
|
|
,
May 3 2018
,
May 3 2018
,
May 3 2018
,
May 4 2018
,
May 8 2018
,
May 11 2018
,
May 17 2018
,
May 18 2018
,
May 18 2018
BTW: Please also note the summary of performance results in go/site-isolation-performance
,
May 21 2018
,
May 21 2018
,
May 23 2018
,
Jun 14 2018
,
Aug 8
|
||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||
Comment 1 by alex...@chromium.org
, May 3 2018