[Webkit-unassigned] [Bug 95758] [chromium] Adjust texture priorities in preparation of impl-thread eviction of only some textures

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=95758





--- Comment #10 from Christopher Cameron <ccameron at chromium.org>  2012-09-04 18:23:12 PST ---
(In reply to comment #9)
> (From update of attachment 162121 [details])
> View in context: https://bugs.webkit.org/attachment.cgi?id=162121&action=review
> 
> I see the issue, but doesn't this just push the problem to the lingering tiles? There could be unbounded lingering tiles as well which would consume all memory, including the 'far' tile memory (which would more likely be closer than the lingering tiles).
>
> What about setting the limit to be some multiple * visibleMemory, to reduce the total memory usage. This will mimic and LRU since all lingering tiles slowly decrease in priority.

Yes -- eventually, you'll hit a hard limit for all memory allowed to be allocated.  When we set the "priority limit", we may want to set it to be "lingering for X frames", which will allow them to be purged more aggressively.

> > I wanted to do this, but the normalization is different in X and Y (so I can't recover it directly from the scalar distance).  I've added a comment about L1 norms because it's you're right that it's unclear what the math does without that prior.
> 
> Hmm, how about reducing to one viewport scaler (average or sum?). In particular a wide viewport shouldn't bias towards caching horizontal tiles.

Oh -- the current scheme is to treat the dimensions separately, so a wide viewport is only taken into account when looking at the horizontal distance to the viewport (and a tall viewport is only taken into account when looking at the vertical distance).

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.