git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Holger Hellmuth (IKS)" <hellmuth@ira.uka.de>
To: "Constantine A. Murenin" <mureninc@gmail.com>
Cc: Charles McGarvey <chazmcgarvey@brokenzipper.com>,
	Fredrik Gustafsson <iveqy@iveqy.com>,
	git@vger.kernel.org
Subject: Re: is there a fast web-interface to git for huge repos?
Date: Fri, 14 Jun 2013 12:55:40 +0200	[thread overview]
Message-ID: <51BAF6AC.2080504@ira.uka.de> (raw)
In-Reply-To: <CAPKkNb460fNJcwt6084xkuDa2sWMRnF+FBu+i_G01aJMMiRevA@mail.gmail.com>

Am 07.06.2013 22:21, schrieb Constantine A. Murenin:
> I'm totally fine with daily updates; but I think there still has to be
> some better way of doing this than wasting 0.5s of CPU time and 5s of
> HDD time (if completely cold) for each blame / log, at the price of
> more storage and some pre-caching, and (daily (in my use-case))
> fine-grained incremental updates.

To get a feel for the numbers: I would guess 'git blame' is mostly run 
against the newest version and the release version of a file, right? I 
couldn't find the number of files in bsd, so lets take linux instead: 
That is 25k files for version 2.6.27. Lets say 35k files altogether for 
both release and newer versions of the files.

A typical page of git blame output on github seems to be in the vicinity 
of 500 kbytes, but that seems to include lots of overhead for comfort 
functions. At least that means it is a good upper bound value.

35k files times 500k gives 17.5 Gbytes, a trivial value for a static 
*disk* based cache. It is also a manageable value for affordable SSDs

      reply	other threads:[~2013-06-14 10:55 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
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) [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=51BAF6AC.2080504@ira.uka.de \
    --to=hellmuth@ira.uka.de \
    --cc=chazmcgarvey@brokenzipper.com \
    --cc=git@vger.kernel.org \
    --cc=iveqy@iveqy.com \
    --cc=mureninc@gmail.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).