From: cgit at cryptocrack.de (Lukas Fleischer)
Subject: Intelligent caching
Date: Tue, 18 Feb 2014 12:48:32 +0100 [thread overview]
Message-ID: <20140218114832.5382.54185@typhoon.lan> (raw)
In-Reply-To: <CAHmME9pnwMN3+sqNSYnZmdKDRpHV6-LJzSdHzkC97EXScB1zUg@mail.gmail.com>
On Thu, 06 Feb 2014 at 20:55:14, Jason A. Donenfeld wrote:
> This could be clever, if it's done properly. It'd have to be something
> along the lines of "this page won't ever change, unless you can create an
> sha1 hash collision", and we'd have to be certain that such pages then only
> use information out of that sha1 object, and not additional related objects
> that can be changed.
> [...]
I started to work on this. The main difficulty is that currently, the
caching layer currently sits on top of prepare_repo_cmd() and is
executed at a very early stage when there is no still no access to the
Git repository. So before implementing this, I guess that we should
check whether the caching mechanism can be moved without performance
impacts (someone needs to review the code and benchmark this).
For now, I will just merge the patches that have been sitting in
lf/staging for several days.
prev parent reply other threads:[~2014-02-18 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 10:18 cgit
2014-02-06 19:55 ` Jason
2014-02-18 11:48 ` cgit [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140218114832.5382.54185@typhoon.lan \
--to=cgit@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).