git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Petr Baudis <pasky@suse.cz>
Cc: Junio C Hamano <junkio@cox.net>, <git@vger.kernel.org>
Subject: Re: [PATCH] gitweb: Support caching projects list
Date: Sat, 15 Mar 2008 14:44:42 -0700 (PDT)	[thread overview]
Message-ID: <m3ve3nwtl3.fsf@localhost.localdomain> (raw)
In-Reply-To: <20080313231413.27966.3383.stgit@rover>

Petr Baudis <pasky@suse.cz> writes:

> On repo.or.cz (permanently I/O overloaded and hosting 1050 project +
> forks), 

It looks like repo.or.cz is overwhelmed by its success. I hope that
now that there are other software hosting sites with git hosting
(Savannah, GitHub, Gitorious,...) the number of projects wouldn't grow
as rapidly.

> the projects list (the default gitweb page) can take more than
> a minute to generate. This naive patch adds simple support for caching
> the projects list data structure so that all the projects do not need
> to get rescanned at every page access.

Another solution would be to divide projects list page into pages,
perhaps adding search box for searching for a project (by name, by
description and by owner).

Nevertheless even with pagination, if we want to have "sort by last
update" we do need caching.

[...]
> +# projects list cache for busy sites with many projects;
> +# if you set this to non-zero, it will be used as the cached
> +# index lifetime in minutes
> +# the cached list version is stored in /tmp and can be tweaked
> +# by other scripts running with the same uid as gitweb - use this
> +# only at secure installations; only single gitweb project root per
> +# system is supported!
> +our $projlist_cache_lifetime = 0;

[...]
> +sub git_project_list_body {
[...]
> +	my $cache_file = '/tmp/gitweb.index.cache';
> +	use File::stat;
> +
> +	my @projects;
> +	my $stale = 0;
> +	if ($cache_lifetime and -f $cache_file
> +	    and stat($cache_file)->mtime + $cache_lifetime * 60 > time()
> +	    and open (my $fd, $cache_file)) {
> +		$stale = time() - stat($cache_file)->mtime;
> +		my @dump = <$fd>;
> +		close $fd;
> +		# Hack zone start
> +		my $VAR1;
> +		eval join("\n", @dump);
> +		@projects = @$VAR1;
> +		# Hack zone end
> +	} else {
> +		if ($cache_lifetime and -f $cache_file) {
> +			# Postpone timeout by two minutes so that we get
> +			# enough time to do our job.
> +			my $time = time() - $cache_lifetime + 120;
> +			utime $time, $time, $cache_file;
> +		}
> +		@projects = git_get_projects_details($projlist, $check_forks);
> +		if ($cache_lifetime and open (my $fd, '>'.$cache_file)) {
> +			use Data::Dumper;
> +			print $fd Dumper(\@projects);
> +			close $fd;
> +		}
> +	}

This could be much simplified with perl-cache (perl-Cache-Cache).
Unfortunately this is non-standard module, not distributed (yet?)
with Perl.

Warning: not tested in gitweb!

+	use Cache::FileCache;
+
+	my $cache;
+	my $projects;
+	
+	if ($cache_lifetime) {
+		$cache = new Cache::FileCache(
+			{ namespace => 'gitweb',
+			  default_expires_in => $cache_lifetime
+			});
+		$projects = $cache->get('projects_list');
+	}
+	if (!defined $projects) {
+		$projects = [ git_get_projects_details($projlist, $check_forks); ];
+		$cache->set('projects_list', $projects)
+			if defined $cache;
+	}

-- 
Jakub Narebski
Poland
ShadeHawk on #git

  parent reply	other threads:[~2008-03-15 21:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13 23:14 [PATCH] gitweb: Support caching projects list Petr Baudis
2008-03-14  0:07 ` Jay Soffian
2008-03-14  0:22   ` Petr Baudis
2008-03-14  0:27     ` Jay Soffian
2008-03-14  0:30       ` J.H.
2008-03-14 12:17         ` Jakub Narebski
2008-03-14  0:36     ` J.H.
2008-03-17 17:49       ` repo.or.cz renovation Petr Baudis
2008-03-17 18:11         ` Petr Baudis
2008-03-17 18:44         ` J.H.
2008-03-17 20:41           ` Jakub Narebski
2008-03-17 21:09           ` Jakub Narebski
2008-03-14 15:29   ` [PATCH] gitweb: Support caching projects list Jakub Narebski
2008-03-14 21:11     ` Jay Soffian
2008-03-14  0:19 ` Junio C Hamano
2008-03-14  8:35 ` Frank Lichtenheld
2008-03-14 12:14 ` Jakub Narebski
2008-03-17 17:40   ` Petr Baudis
2008-03-15 21:44 ` Jakub Narebski [this message]
2008-03-16  0:56   ` Miklos Vajna
2008-03-16 11:41   ` Frank Lichtenheld
2008-03-16 16:52     ` J.H.
2008-03-16 18:37       ` Jakub Narebski
2008-03-16 22:37         ` J.H.
2008-03-16 23:39           ` Jakub Narebski
2008-03-17 18:10   ` repo.or.cz renovated Petr Baudis
2008-03-17 19:09     ` Junio C Hamano
2008-03-17 19:25       ` Petr Baudis
2008-03-17 19:34     ` Theodore Tso
2008-03-17 19:54       ` Petr Baudis

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=m3ve3nwtl3.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=pasky@suse.cz \
    /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).