"J.H." <warthog19@xxxxxxxxxxxxxx> writes: > Joey Hess wrote: >> Giuseppe Bilotta wrote: >> >>>> There is a small overhead in including the microformat on project list >>>> and forks list pages, but getting the project descriptions for those pages >>>> already incurs a similar overhead, and the ability to get every repo url >>>> in one place seems worthwhile. >>>> >>> I agree with this, although people with very large project lists may >>> differ ... do we have timings on these? >>> >> >> AFAICS, when displaying the project list, gitweb reads each project's >> description file, falling back to reading its config file if there is no >> description file. >> >> If performance was a problem here, the thing to do would be to add >> project descriptions to the $project_list file, and use those in >> preference to the description files. If a large site has done that, >> they've not sent in the patch. :-) > > No because all the large sites have pain points and issues elsewhere > in the app. Most of the large sites (which I can at least speak for > Kernel.org) went and have built in full caching layers into gitweb > itself to deal with the problem. This means that we don't have to > worry about nickle and dime performance improvements that are specific > to one section, but can do a very broad sweep and get dramatically > better performance across all of gitweb. Those patches have all made > it back out onto the mailing list, but for a number of different > reasons none have been accepted into the mainline branch. Additional issue is that when you add or delete repository (project), you have to correct or regenerate projects_index file. While it is I think quite easy for git hosting sites such as repo.or.cz, it is harder for sites which offer gitweb just like they ofer WWW homepages: as a service, with repositories created (and descriptions updated) outside of gitweb control. -- Jakub Narebski Poland ShadeHawk on #git -- 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
