<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 02/03/2018 10:12 PM, Dominik Ruf
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAAfZa5mzaaPCw6epvkfwr68bxnnppXLAJSQGeyhXuu_o57Bnbw@mail.gmail.com">
<div dir="ltr"><br>
<div class="gmail_quote">
<div dir="ltr">Mads Kiilerich <<a
href="mailto:mads@kiilerich.com" moz-do-not-send="true">mads@kiilerich.com</a>>
schrieb am Sa., 3. Feb. 2018 um 19:32 Uhr:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">On
02/01/2018 12:50 AM, Dominik Ruf wrote:<br>
> Hi all,<br>
><br>
> I'm currently looking at the caching Kallithea does.
And I'm a<br>
> bit...baffled.<br>
<br>
Yes, it is quite baffling and not very efficient.<br>
<br>
I think it very rarely gives any real benefit - it might
even make<br>
things slower. In real world setups with multiple
repositories served by<br>
each worker process, cache hits are quite rare.</blockquote>
<div>For large git repositories we certainly do need caching.</div>
</div>
</div>
</blockquote>
<br>
Perhaps. But it is probably a very different kind of caching we
need.<br>
<br>
/Mads
</body>
</html>