git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J.H." <warthog19@eaglescrag.net>
To: Bruno Cesar Ribas <ribas@c3sl.ufpr.br>
Cc: Jakub Narebski <jnareb@gmail.com>,
	git@vger.kernel.org, Petr Baudis <pasky@suse.cz>
Subject: Re: Another bench on gitweb (also on gitweb caching)
Date: Tue, 12 Feb 2008 16:57:30 -0800	[thread overview]
Message-ID: <1202864250.17207.22.camel@localhost.localdomain> (raw)
In-Reply-To: <20080213004528.GB31455@c3sl.ufpr.br>

 
> > > I found out those VERY interesting, so instead of trying to think a
> > > new way to store gitweb config, we should think a way to cache those
> > > information.
> > 
> > Below there are my thoughts about caching information for gitweb:
> > 
> > First, the basis of each otimisation is checking the bottlenecks.
> > I think it was posted sometime there that the pages taking most load
> > are projects list and feeds. 
> > 
> > Kernel.org even run modified version of gitweb, with some caching
> > support; Cgit (git web interface in C) also has caching support.
> 
> Is this gitweb version for kernel.org available somewhere?
> > 
> > 

It's available from my git tree on kernel.org
http://git.kernel.org/?p=git/warthog9/gitweb.git;a=summary

or

git://git.kernel.org/pub/scm/git/warthog9/gitweb.git

Mind you my performance on the non-cache state is not going to be any
better than normal gitweb, however the performance on a cache-hit is
orders of magnitude faster - though at a rather expensive cost - disk
space.  There is currently something like 20G of disk being used on one
of kernel.org's machines providing the cache (this does get flushed on
occasion - I think) but that is providing caching for everything that
kernel.org has in it's git trees (or 255188 unique urls currently).  My
code base is now, horribly, out of date with respect to mainline but it
works and it's been solid and reasonably reliable (though I do know of
two bugs in it right now I need to track down - one with respect to a
failure of the script - and one that is an array out of bounds error)

- John

  parent reply	other threads:[~2008-02-13  1:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-10  3:09 Another bench on gitweb Bruno Cesar Ribas
2008-02-12  0:44 ` Another bench on gitweb (also on gitweb caching) Jakub Narebski
2008-02-13  0:45   ` Bruno Cesar Ribas
2008-02-13  0:50     ` Bruno Cesar Ribas
2008-02-13  0:57     ` J.H. [this message]
2008-02-13  1:01     ` J.H.
2008-02-13 12:17       ` Jakub Narebski
2008-02-13 19:12         ` J.H.
2008-02-14  1:01           ` Jakub Narebski
2008-02-14 22:43             ` J.H.
2008-02-15 23:19               ` Jakub Narebski

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=1202864250.17207.22.camel@localhost.localdomain \
    --to=warthog19@eaglescrag.net \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=pasky@suse.cz \
    --cc=ribas@c3sl.ufpr.br \
    /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).