On Fri, 10 Sep 2010, J.H. wrote: > On 09/10/2010 11:57 AM, Jakub Narebski wrote: > > Lubomir Rintel <lkundrak@xxxxx> writes: > > > > > I thought something like this could be a starter for better handling long > > > gitweb project lists (such as http://pkgs.fedoraproject.org/gitweb/). > > > > > > Could anyone please take a look? > > > > What do you mean here by "better handling"? > > > > Is the problem server performance for large number of projects? If > > this is the problem, perhaps better solution would be to use caching > > (work in progress). > > They already moved to using my caching layer, mainly because I could > create an RPM for them and the fact that my caching code is slightly > more battle tested. Note that with project list pagination, and especially with project search feature, a better solution might be to cache *data* rather than HTML output, like in fork used (or used to be used) by http://repo.or.cz, or in Lea Wiemann's GSoC 2008 project [1] [1] http://repo.or.cz/w/git/gitweb-caching.git -- Jakub Narebski Poland -- 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