There has been some recent discussion concerning the amount of resources that gitweb is chewing through, particularly on kernel.org. I've just pushed a small set of changes out to kernel.org that add in caching to the gitweb thats running on it. Changes are published at git://git.kernel.org/pub/scm/git/warthog9/gitweb.git
Thoughts or comments are welcome.
- John 'Warthog9'
Re: Gitweb - caching
> Thoughts or comments are welcome.
Interesting work, John. Some initial comments:
* It's a very intrusive set of changes. * An infinite expiry date isn't valid for all pages. * The other HTTP headers can change depending on the page returned. * A single cache directory is going to have problems as the number of cached files grows.
What are the benefits of doing this inside of gitweb instead of using something like mod_cache or mod_perl handlers?
Robert
Re: Gitweb - caching
Robert Fitzsimons wrote:
>> Thoughts or comments are welcome. > > Interesting work, John. Some initial comments: > > * It's a very intrusive set of changes. > * An infinite expiry date isn't valid for all pages. > * The other HTTP headers can change depending on the page returned. > * A single cache directory is going to have problems as the number of > cached files grows. > > What are the benefits of doing this inside of gitweb instead of using > something like mod_cache or mod_perl handlers?
Or wrapping the gitweb output inside cgicache: http://linux.yyz.us/projects.html
Jeff
Jakub NarebskiRe: Gitweb - caching
Robert Fitzsimons wrote:
> * An infinite expiry date isn't valid for all pages.
An infinite expiry date is not valid at all. IIRC HTTP defines that "infinite" expiry is one year.
-- Jakub Narebski Warsaw, Poland ShadeHawk on #git