From: "H. Peter Anvin" <hpa@zytor.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: gitweb.cgi
Date: Tue, 18 Oct 2005 10:24:18 -0700 [thread overview]
Message-ID: <43552FC2.3000000@zytor.com> (raw)
In-Reply-To: <20051018110725.GB6929@vrfy.org>
Kay Sievers wrote:
>
>>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 ... :)
>
Welcome to my hell :)
I set up mod_cache (which I didn't know about, silly me) and so far it
seems to work and has produced a tremendous decrease in load and
improvement in response time. I do, have, however, a request. There
are some gitweb pages which are more likely to change than others; in
particular, some gitweb pages will *never* change (because they directly
reflect immutable git data.)
If gitweb could produce Last-Modified and Expires headers where
appropriate, it should improve caching performance.
-hpa
next prev parent reply other threads:[~2005-10-18 17:24 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 ` gitweb.cgi Kay Sievers
2005-10-18 16:52 ` gitweb.cgi H. Peter Anvin
2005-10-18 17:24 ` H. Peter Anvin [this message]
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=43552FC2.3000000@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.org \
--cc=kay.sievers@vrfy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.