[Webkit-unassigned] [Bug 200159] Make NetworkCache cache shrink logic take account of the configured capacity

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jul 26 06:46:21 PDT 2019


--- Comment #5 from Loïc Yhuel <loic.yhuel at softathome.com> ---
(In reply to Chris Dumez from comment #4)
> > Source/WebKit/ChangeLog:9
> > +        more than 33%, we should target 67% of the capacity instead.
> Why? 
> This change log does not explain why this change is needed.
It's "when reducing the cache capacity". The target shrink size must depend on the desired capacity, not the current size.

For example if you have a 200MB cache (capacity >= 200MB), and you call WebKit::NetworkCache::Cache::setCapacity(100MB), the original code has a maximum deletion probability of 33% so to cache would be reduced to 134MB at best, so you would need at laest a second shrink to be under 100MB.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190726/571c3aee/attachment.html>

More information about the webkit-unassigned mailing list