From: Linus Torvalds <torvalds@osdl.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Kernel Org Admin <ftpadmin@kernel.org>,
Git Mailing List <git@vger.kernel.org>,
Jakub Narebski <jnareb@gmail.com>
Subject: Re: kernel.org mirroring (Re: [GIT PULL] MMC update)
Date: Thu, 7 Dec 2006 11:05:59 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0612071052560.3615@woody.osdl.org> (raw)
In-Reply-To: <45785697.1060001@zytor.com>
On Thu, 7 Dec 2006, H. Peter Anvin wrote:
>
> That all being said, the lack of intrinsic caching in gitweb continues to be a
> major problem for us. Under high load, it makes all the problems worse.
I really don't see what gitweb could do that would be somehow better than
apache doing the caching in front of it.. Is there some apache reason why
that isn't sufficient (ie limitations on its cache size or timeouts?)
Maybe the cacheability hints from gitweb could be tweaked (a lot of it
should be "infinitely cacheable", but the stuff that depends on refs and
thus can change, could be set to some fixed host-wide value - preferably
some that depends on how old the ref is).
Having gitweb be potentially up to an hour out of date is better than
causing mirroring problems due to excessive load.
For example, if the git "refs/heads/" (or tags) directory hasn't changed
in the last two months, we should probably set any ref-relative gitweb
pages to have a caching timeout of a day or two. In contrast, if it's
changed in the last hour, maybe we should only cache it for five minutes.
Jakub: any way to make gitweb set the "expires" fields _much_ more
aggressively. I think we should at least have the ability to set a basic
rules like
- a _minimum_ of five minutes regardless of anything else
We might even tweak this based on loadaverage, and it might be
worthwhile to add a randomization, to make sure that you don't get into
situations where everything webpage needs to be recalculated at once.
- if refs/ directories are old, raise the minimum by the age of the refs
If it's more than an hour old, raise it to ten minutes. If it's more
than a day, raise it to an hour. If it's more than a month old, raise
it to a day. And if it's more than half a year, it's some historical
archive like linux-history, and should probably default to a week or
more.
- infinite for stuff that isn't ref-related.
Hmm?
next parent reply other threads:[~2006-12-07 19:08 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45708A56.3040508@drzeus.cx>
[not found] ` <Pine.LNX.4.64.0612011639240.3695@woody.osdl.org>
[not found] ` <457151A0.8090203@drzeus.cx>
[not found] ` <Pine.LNX.4.64.0612020835110.3476@woody.osdl.org>
[not found] ` <45744FA3.7020908@zytor.com>
[not found] ` <Pine.LNX.4.64.0612061847190.3615@woody.osdl.org>
[not found] ` <45778AA3.7080709@zytor.com>
[not found] ` <Pine.LNX.4.64.0612061940170.3615@woody.osdl.org>
[not found] ` <4577A84C.3010601@zytor.com>
[not found] ` <Pine.LNX.4.64.0612070953290.3615@woody.osdl.org>
[not found] ` <45785697.1060001@zytor.com>
2006-12-07 19:05 ` Linus Torvalds [this message]
2006-12-07 19:16 ` kernel.org mirroring (Re: [GIT PULL] MMC update) H. Peter Anvin
2006-12-07 19:30 ` Olivier Galibert
2006-12-07 19:57 ` H. Peter Anvin
2006-12-07 23:50 ` Olivier Galibert
2006-12-07 23:56 ` H. Peter Anvin
2006-12-08 11:25 ` Jakub Narebski
2006-12-08 12:57 ` Rogan Dawes
2006-12-08 13:38 ` Jakub Narebski
2006-12-08 14:31 ` Rogan Dawes
2006-12-08 15:38 ` Jonas Fonseca
2006-12-09 1:28 ` Martin Langhoff
2006-12-09 2:03 ` H. Peter Anvin
2006-12-09 2:52 ` Martin Langhoff
2006-12-09 5:09 ` H. Peter Anvin
2006-12-09 5:34 ` Martin Langhoff
2006-12-09 16:26 ` H. Peter Anvin
2006-12-08 16:16 ` H. Peter Anvin
2006-12-08 16:35 ` Linus Torvalds
2006-12-08 16:42 ` H. Peter Anvin
2006-12-08 19:49 ` Lars Hjemli
2006-12-08 19:51 ` H. Peter Anvin
2006-12-08 19:59 ` Lars Hjemli
2006-12-08 20:02 ` H. Peter Anvin
2006-12-10 9:43 ` rda
2006-12-08 16:54 ` Jeff Garzik
2006-12-08 17:04 ` H. Peter Anvin
2006-12-08 17:40 ` Jeff Garzik
2006-12-08 23:27 ` Linus Torvalds
2006-12-08 23:46 ` Michael K. Edwards
2006-12-08 23:49 ` H. Peter Anvin
2006-12-09 0:18 ` Michael K. Edwards
2006-12-09 0:23 ` H. Peter Anvin
2006-12-09 0:49 ` Linus Torvalds
2006-12-09 0:51 ` H. Peter Anvin
2006-12-09 4:36 ` Michael K. Edwards
2006-12-09 9:27 ` Jeff Garzik
[not found] ` <4579FABC.5070509@garzik.org>
2006-12-09 0:45 ` Linus Torvalds
2006-12-09 0:47 ` H. Peter Anvin
2006-12-09 9:16 ` Jeff Garzik
2006-12-09 1:56 ` Martin Langhoff
2006-12-09 11:51 ` Jakub Narebski
2006-12-09 12:42 ` Jeff Garzik
2006-12-09 13:37 ` Jakub Narebski
2006-12-09 14:43 ` Jeff Garzik
2006-12-09 17:02 ` Jakub Narebski
2006-12-09 17:27 ` Jeff Garzik
2006-12-10 4:07 ` Martin Langhoff
2006-12-10 10:09 ` Jakub Narebski
2006-12-10 12:41 ` Jeff Garzik
2006-12-10 13:02 ` Jakub Narebski
2006-12-10 13:45 ` Jeff Garzik
2006-12-10 19:11 ` Jakub Narebski
2006-12-10 19:50 ` Linus Torvalds
2006-12-10 20:27 ` Jakub Narebski
2006-12-10 20:30 ` Linus Torvalds
2006-12-10 22:01 ` Martin Langhoff
2006-12-10 22:14 ` Jeff Garzik
2006-12-10 22:08 ` Jeff Garzik
2006-12-10 21:01 ` H. Peter Anvin
2006-12-10 22:05 ` Jeff Garzik
2006-12-10 22:59 ` Jakub Narebski
2006-12-11 2:16 ` Martin Langhoff
2006-12-11 8:59 ` Jakub Narebski
2006-12-11 10:18 ` Martin Langhoff
2006-12-09 18:04 ` Linus Torvalds
2006-12-09 18:30 ` H. Peter Anvin
2006-12-10 3:55 ` Martin Langhoff
2006-12-10 7:05 ` H. Peter Anvin
2006-12-12 21:19 ` Jakub Narebski
2006-12-09 7:56 ` Steven Grimm
2006-12-07 19:30 ` Linus Torvalds
2006-12-07 19:39 ` Shawn Pearce
2006-12-07 19:58 ` Linus Torvalds
2006-12-07 23:33 ` Michael K. Edwards
2006-12-07 19:58 ` H. Peter Anvin
2006-12-07 20:05 ` Junio C Hamano
2006-12-07 20:09 ` H. Peter Anvin
2006-12-07 22:11 ` Junio C Hamano
2006-12-08 9:43 ` Jakub Narebski
2006-12-11 3:40 linux
2006-12-11 9:30 ` 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=Pine.LNX.4.64.0612071052560.3615@woody.osdl.org \
--to=torvalds@osdl.org \
--cc=ftpadmin@kernel.org \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=jnareb@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).