From: "Constantine A. Murenin" <mureninc@gmail.com>
To: Fredrik Gustafsson <iveqy@iveqy.com>
Cc: git@vger.kernel.org
Subject: Re: is there a fast web-interface to git for huge repos?
Date: Fri, 7 Jun 2013 10:05:37 -0700 [thread overview]
Message-ID: <CAPKkNb5PyurX1eNsCsckdfiwgM3dqb5KpN9OS0NpLZw1+VsSdg@mail.gmail.com> (raw)
In-Reply-To: <20130607063353.GB19771@paksenarrion.iveqy.com>
On 6 June 2013 23:33, Fredrik Gustafsson <iveqy@iveqy.com> wrote:
> On Thu, Jun 06, 2013 at 06:35:43PM -0700, Constantine A. Murenin wrote:
>> I'm interested in running a web interface to this and other similar
>> git repositories (FreeBSD and NetBSD git repositories are even much,
>> much bigger).
>>
>> Software-wise, is there no way to make cold access for git-log and
>> git-blame to be orders of magnitude less than ~5s, and warm access
>> less than ~0.5s?
>
> The obvious way would be to cache the results. You can even put an
That would do nothing to prevent slowness of the cold requests, which
already run for 5s when completely cold.
In fact, unless done right, it would actually slow things down, as
lines would not necessarily show up as they're ready.
> update cache hook the git repositories to make the cache always be up to
> date.
That's entirely inefficient. It'll probably take hours or days to
pre-cache all the html pages with a naive wget and the list of all the
files. Not a solution at all.
(0.5s x 35k files = 5 hours for log/blame, plus another 5h of cpu time
for blame/log)
> There's some dynamic web frontends like cgit and gitweb out there but
> there's also static ones like git-arr ( http://blitiri.com.ar/p/git-arr/
> ) that might be more of an option to you.
The concept for git-arr looks interesting, but it has neither blame
nor log, so, it's kinda pointless, because the whole thing that's slow
is exactly blame and log.
There has to be some way to improve these matters. Noone wants to
wait 5 seconds until a page is generated, we're not running enterprise
software here, latency is important!
C.
next prev parent reply other threads:[~2013-06-07 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 1:35 is there a fast web-interface to git for huge repos? Constantine A. Murenin
2013-06-07 6:33 ` Fredrik Gustafsson
2013-06-07 17:05 ` Constantine A. Murenin [this message]
2013-06-07 17:57 ` Fredrik Gustafsson
2013-06-07 19:02 ` Constantine A. Murenin
2013-06-07 20:13 ` Charles McGarvey
2013-06-07 20:21 ` Constantine A. Murenin
2013-06-14 10:55 ` Holger Hellmuth (IKS)
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=CAPKkNb5PyurX1eNsCsckdfiwgM3dqb5KpN9OS0NpLZw1+VsSdg@mail.gmail.com \
--to=mureninc@gmail.com \
--cc=git@vger.kernel.org \
--cc=iveqy@iveqy.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).