Caching: simple backend status

[Cedric Berndt]

I was looking into Chrome caching behavior recently, trying to explain why some of our payloads seemed to be evicted more quickly than expected.  From what I can tell, it looks like my machine (Chrome 76.0.3809.100 on Ubuntu 18.04.2) is using the very simple backend while my colleague's machine (Chrome 76.0.3809.100 on Windows 10) still seems to be using the original block file implementation.  This was surprising to me because it looked like the push to migrate to the simple backend started back in 2013.

Would someone be able to provide me with some context here?

[Torne (Richard Coles)]

The block file implementation is still used for Windows and OSX because on those platforms it's still faster.. Only the other platforms (Linux, Android, etc) have moved to the simple cache backend.

On Wed, 21 Aug 2019 at 01:50, Cedric Berndt <berndt...@gmail.com> wrote:

I was looking into Chrome caching behavior recently, trying to explain why some of our payloads seemed to be evicted more quickly than expected.  From what I can tell, it looks like my machine (Chrome 76.0.3809.100 on Ubuntu 18.04.2) is using the very simple backend while my colleague's machine (Chrome 76.0.3809.100 on Windows 10) still seems to be using the original block file implementation.  This was surprising to me because it looked like the push to migrate to the simple backend started back in 2013.

Would someone be able to provide me with some context here?

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss