From: Kay Sievers <kay.sievers@vrfy.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: gitweb.cgi
Date: Tue, 18 Oct 2005 13:07:25 +0200 [thread overview]
Message-ID: <20051018110725.GB6929@vrfy.org> (raw)
In-Reply-To: <43546492.3020401@zytor.com>
On Mon, Oct 17, 2005 at 07:57:22PM -0700, H. Peter Anvin wrote:
> It is increasingly clear that gitweb.cgi is producing an unacceptable
> load on the kernel.org servers.
Sure, sorry, was on 3 conferences in a row the last weeks.
> Most of the hits we get are either the
> gitweb front page or the gitweb rss feeds, and it's eating I/O bandwidth
> like crazy.
I tested some stuff on these boxes and 30 stat() calls alone take app. 2 seconds
on these boxes cause of I/O load ... :)
> This has become particularly painful during the current one-server outage.
>
> Kay, gitweb really needs to be able to do caching, or be run behind a
> caching proxy. Otherwise I will have to turn it off until we can come
> up with a dedicated piece of server hardware for it.
How about Apache's mod_cache? Worked nicely for me several times in other
setups.
Kay
next prev parent reply other threads:[~2005-10-18 11:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 2:57 gitweb.cgi H. Peter Anvin
2005-10-18 11:07 ` Kay Sievers [this message]
2005-10-18 16:52 ` gitweb.cgi H. Peter Anvin
2005-10-18 17:24 ` gitweb.cgi H. Peter Anvin
2005-10-18 20:44 ` gitweb.cgi Brian Gerst
2005-10-19 0:27 ` gitweb.cgi Linus Torvalds
2005-10-19 0:30 ` gitweb.cgi H. Peter Anvin
2005-10-19 0:53 ` Optimize common case of git-rev-list (was Re: gitweb.cgi) Linus Torvalds
2005-10-19 0:38 ` gitweb.cgi H. Peter Anvin
2005-10-19 1:02 ` gitweb.cgi Linus Torvalds
2005-10-19 1:14 ` gitweb.cgi H. Peter Anvin
2005-10-19 13:59 ` gitweb.cgi Linus Torvalds
2005-10-19 16:16 ` gitweb.cgi H. Peter Anvin
2005-10-19 1:23 ` gitweb.cgi Kay Sievers
2005-10-19 1:33 ` gitweb.cgi Kay Sievers
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=20051018110725.GB6929@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.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).