<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Network Cache: Disk cache getting filled by YouTube video data"
href="https://bugs.webkit.org/show_bug.cgi?id=144259#c15">Comment # 15</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Network Cache: Disk cache getting filled by YouTube video data"
href="https://bugs.webkit.org/show_bug.cgi?id=144259">bug 144259</a>
from <span class="vcard"><a class="email" href="mailto:koivisto@iki.fi" title="Antti Koivisto <koivisto@iki.fi>"> <span class="fn">Antti Koivisto</span></a>
</span></b>
<pre><span class="quote">> We don't think that people rewind, fast-forward, and/or revisit videos? I
> tend to do all of those things. :(</span >
At least the current YouTube player never seems to generate the same URL twice so cache entires are never hit. For rewind and fast-forward have 5min 1024p, 314MB memory cache on MSE level (bigger than the entire disk cache).
We can't currently move data from the memory cache to MSE without copying so there is no mapped file benefit either.
We should revisit this at some point. I think we want a separate more transient media cache section on disk and we should allow copy-free use of mapped buffers through the stack.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>