> > > I found out those VERY interesting, so instead of trying to think a > > > new way to store gitweb config, we should think a way to cache those > > > information. > > > > Below there are my thoughts about caching information for gitweb: > > > > First, the basis of each otimisation is checking the bottlenecks. > > I think it was posted sometime there that the pages taking most load > > are projects list and feeds. > > > > Kernel.org even run modified version of gitweb, with some caching > > support; Cgit (git web interface in C) also has caching support. > > Is this gitweb version for kernel.org available somewhere? > > > > It's available from my git tree on kernel.org http://git.kernel.org/?p=git/warthog9/gitweb.git;a=summary or git://git.kernel.org/pub/scm/git/warthog9/gitweb.git Mind you my performance on the non-cache state is not going to be any better than normal gitweb, however the performance on a cache-hit is orders of magnitude faster - though at a rather expensive cost - disk space. There is currently something like 20G of disk being used on one of kernel.org's machines providing the cache (this does get flushed on occasion - I think) but that is providing caching for everything that kernel.org has in it's git trees (or 255188 unique urls currently). My code base is now, horribly, out of date with respect to mainline but it works and it's been solid and reasonably reliable (though I do know of two bugs in it right now I need to track down - one with respect to a failure of the script - and one that is an array out of bounds error) - John - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
