Re: gitweb.cgi
- From
- Kay Sievers <kay.sievers@vrfy.org>
- Date
- Oct 19, 2005, 01:33 UTC
- Message-ID
- <20051019013321.GA10331@vrfy.org>
- In-Reply-To
- <43552FC2.3000000@zytor.com>
On Tue, Oct 18, 2005 at 10:24:18AM -0700, H. Peter Anvin wrote:
Show 12 quoted lines
> 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 :)
Yeah, I get an idea now :)
> 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.
Great! Hope that will work.
> 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.)
Yes, makes sense.
> If gitweb could produce Last-Modified and Expires headers where > appropriate, it should improve caching performance.
I've added the Expires: header to the commit and commitdiff pages with one whole day ahead. Let's see if that will help...
Kay