git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: "J.H." <warthog9@kernel.org>, Petr Baudis <pasky@suse.cz>
Cc: Bruno Cesar Ribas <ribas@c3sl.ufpr.br>, git@vger.kernel.org
Subject: Re: Another bench on gitweb (also on gitweb caching)
Date: Wed, 13 Feb 2008 13:17:46 +0100	[thread overview]
Message-ID: <200802131317.48815.jnareb@gmail.com> (raw)
In-Reply-To: <1202864493.17207.24.camel@localhost.localdomain>

On Wed, 13 Feb 2008, J.H. "Warthog9" wrote:
> Bruno Cesar Ribas <ribas@c3sl.ufpr.br> writes:
>> On Mon, Feb 11, 2008 at 04:44:23PM -0800, Jakub Narebski wrote:

>>> 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)

BTW. did you consider using cgit (C/Caching git web interface) instead
or in addition to gitweb? Freedesktop.org uses it side by side with
gitweb. I wonder how it would perform on kernel.org...

(Almost) every optimization should begin with profiling. Could you tell
us which gitweb pages are most called and perhaps which pages generate
most load for kernel.org? How new projects are added (old projects
deleted)? Do you control (can add to or can add multiplexing) to update
or post-receive hooks?

Without this data we could concentrate on things which are of no
importance. BTW. I wonder if slitting projects_list page would help...

-- 
Jakub Narebski
Poland

  reply	other threads:[~2008-02-13 12:18 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.
2008-02-13  1:01     ` J.H.
2008-02-13 12:17       ` Jakub Narebski [this message]
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=200802131317.48815.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    --cc=ribas@c3sl.ufpr.br \
    --cc=warthog9@kernel.org \
    /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).