From: hjemli at gmail.com (Lars Hjemli)
Subject: Caching TTL values per repository
Date: Mon, 4 Nov 2019 12:27:44 +0100 [thread overview]
Message-ID: <CAFXTnz4VrGrxXUz=4Fq+ELGB2qKsa36D86CZ+rfKbvNgumMzRw@mail.gmail.com> (raw)
In-Reply-To: <CAKcFC3b2hukjQ8q05zbiCEZZ=MXT-agq8nP2a7HN3JKhsRwH1A@mail.gmail.com>
On Thu, Oct 31, 2019 at 7:42 PM jean-christophe manciot
<actionmystique at gmail.com> wrote:
> I have defined some global cache TTL values in /etc/cgitrc:
...
> For a particular repo which is not expected to be modified anytime soon and holds many objects, I have tried to set other values in its own cgitrc:
...
> However, they don't seem effective in the sense that some requests never seem to be cached at all and can take a very long time to complete; for instance, its log.
>
> - Is this behaviour expected because it is not possible to set cache values per repository?
Yes, the cache is shared by all repos so this behaviour is expected.
--
larsh
prev parent reply other threads:[~2019-11-04 11:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 18:41 actionmystique
2019-11-04 11:27 ` hjemli [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='CAFXTnz4VrGrxXUz=4Fq+ELGB2qKsa36D86CZ+rfKbvNgumMzRw@mail.gmail.com' \
--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).