From: lekensteyn at gmail.com (Peter Wu)
Subject: Caching and concurrency?
Date: Sat, 13 Apr 2013 15:54:35 +0200 [thread overview]
Message-ID: <11703865.zzjuJsPtxJ@al> (raw)
Hi,
I was wondering how well the caching mechanism of cgit works. Is it designed
for concurrent access to the cache folders? I am tempted to use nginx cache
mechanism, but a downside of that is that duplicate cache entries may occur
(?id=d34db33f vs ?id=d34db33f000000 are possibly the same, but I guess nginx
sees it as the same) and that entries are at least as old as the nginx cache
expirity time.
Anyway, the questions:
- Is cgits cache immediately updated whenever the git tree is updated? If not,
what delay can I expect?
- Is it better to use a dedicated caching proxy (nginx) instead of cgit when
available?
- How well prepared is cgit for concurrent access?
Of course I should measure it myself too, but are there any obvious points I
should take into account when considering a cache mechanism?
Regards,
Peter
next reply other threads:[~2013-04-13 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 13:54 lekensteyn [this message]
2013-04-13 14:37 ` john
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=11703865.zzjuJsPtxJ@al \
--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).