From: Jakub Narebski <jnareb@gmail.com>
To: "J.H." <warthog19@eaglescrag.net>
Cc: Lubomir Rintel <lkundrak@v3.sk>, git@vger.kernel.org
Subject: Re: [RESEND] Pagination for gitweb
Date: Fri, 10 Sep 2010 23:53:14 +0200 [thread overview]
Message-ID: <201009102353.17279.jnareb@gmail.com> (raw)
In-Reply-To: <4C8A816E.4090305@eaglescrag.net>
On Fri, 10 Sep 2010, J.H. wrote:
> On 09/10/2010 11:57 AM, Jakub Narebski wrote:
> > Lubomir Rintel <lkundrak@v3.sk> 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
next prev parent reply other threads:[~2010-09-10 21:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 16:17 [RESEND] Pagination for gitweb Lubomir Rintel
2010-09-10 16:17 ` [PATCH 1/2] gitweb: Make it possible to paginate projects Lubomir Rintel
2010-09-10 16:17 ` [PATCH 2/2] gitweb: Optimize paging when sorted by path Lubomir Rintel
2010-09-10 19:24 ` Jakub Narebski
2010-09-10 19:10 ` [PATCH 1/2] gitweb: Make it possible to paginate projects Jakub Narebski
2010-09-10 18:57 ` [RESEND] Pagination for gitweb Jakub Narebski
2010-09-10 19:05 ` J.H.
2010-09-10 21:53 ` Jakub Narebski [this message]
2010-09-12 19:40 ` Jakub Narebski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201009102353.17279.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=warthog19@eaglescrag.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).