At the moment, we retain unparented cohorts of tiles for four-ish seconds after they leave the tile coverage rect. However, since the remote layer tree code doesn't support purgeable unparented tiles, this means that scrolling quickly leads to a backing store explosion with no recourse. We should disable tile cohort retention for now (I have confirmed that it hugely improves performance/reduces process death when scrolling quickly). We will enable aggressive tile retention (like Mac uses) once we have purgeable unparented tile support.
<rdar://problem/16465413>
Created attachment 228106 [details] patch
(In reply to comment #0) > ...retain unparented cohorts of tiles for four-ish seconds after they leave... two-ish actually
Comment on attachment 228106 [details] patch I thought this would be just prefs change but there are a bunch of structural changes that I don't entirely follow. If I'm understanding this correctly, what this patch actually seems to do is introduce a new setting that retains tile cohorts temporarily instead of indefinitely. Is that correct? I'm not sure "disable tile cohort retention for now" is the clearest way to express that.
(In reply to comment #4) > (From update of attachment 228106 [details]) > I thought this would be just prefs change but there are a bunch of structural changes that I don't entirely follow. If I'm understanding this correctly, what this patch actually seems to do is introduce a new setting that retains tile cohorts temporarily instead of indefinitely. Is that correct? I'm not sure "disable tile cohort retention for now" is the clearest way to express that. No, it adds a new setting (which previously was not a setting, just was always true) to enable temporary retention, and turns that setting *off* on iOS. Thus, disabling retention of cohorts. There has long been a setting for indefinite ("aggressive") retention, and that one is off by default as well (but gets turned on on Mac by clients).
http://trac.webkit.org/changeset/166516