From: Jakub Narebski <jnareb@gmail.com>
To: Lubomir Rintel <lkundrak@v3.sk>
Cc: git@vger.kernel.org
Subject: Re: [RESEND] Pagination for gitweb
Date: Fri, 10 Sep 2010 11:57:44 -0700 (PDT) [thread overview]
Message-ID: <m34odxmnpj.fsf@localhost.localdomain> (raw)
In-Reply-To: <1284135442-10971-1-git-send-email-lkundrak@v3.sk>
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).
Is the problem large projects-list page and bandwidth? There was a
patch adding transparent compression of pages generated by gitweb
would be a better solution; perhaps this together with caching (to
avoid performance hit on CPU; note that usually gitweb performance is
I/O and not CPU-bound).
Is the problem client rendering performance on large page with large
table? If it is, then paginating output, or adding project search
like in gitweb fork used on http://repo.or.cz is correct solution.
So which is it?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-09-10 18:57 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 ` Jakub Narebski [this message]
2010-09-10 19:05 ` [RESEND] Pagination for gitweb J.H.
2010-09-10 21:53 ` Jakub Narebski
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=m34odxmnpj.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=lkundrak@v3.sk \
/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).