Current caching
Dominik Ruf
dominikruf at gmail.com
Sun Feb 4 11:31:49 UTC 2018
On Sun, Feb 4, 2018, 12:03 Mads Kiilerich <mads at kiilerich.com> wrote:
> On 02/03/2018 10:12 PM, Dominik Ruf wrote:
>
>
> Mads Kiilerich <mads at kiilerich.com> schrieb am Sa., 3. Feb. 2018 um
> 19:32 Uhr:
>
>> On 02/01/2018 12:50 AM, Dominik Ruf wrote:
>> > Hi all,
>> >
>> > I'm currently looking at the caching Kallithea does. And I'm a
>> > bit...baffled.
>>
>> Yes, it is quite baffling and not very efficient.
>>
>> I think it very rarely gives any real benefit - it might even make
>> things slower. In real world setups with multiple repositories served by
>> each worker process, cache hits are quite rare.
>
> For large git repositories we certainly do need caching.
>
>
> Perhaps. But it is probably a very different kind of caching we need.
>
Displaying a changelog page with 100 changesets currently takes 54 seconds
even with the current caching for the Linux Kernel.
I'm about to make some changes that will get this down to about 2.5
seconds. But of course this also depends on caching.
>
>
> /Mads
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sfconservancy.org/pipermail/kallithea-general/attachments/20180204/c4901622/attachment.html>
More information about the kallithea-general
mailing list