From: Jakub Narebski <jnareb@gmail.com>
To: "J.H." <warthog19@eaglescrag.net>
Cc: Joey Hess <joey@kitenet.net>,
git@vger.kernel.org,
Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Subject: Re: gitweb index performance (Re: [PATCH] gitweb: support the rel=vcs-* microformat)
Date: Fri, 09 Jan 2009 17:44:50 -0800 (PST) [thread overview]
Message-ID: <m3y6xkylwu.fsf@localhost.localdomain> (raw)
In-Reply-To: <496691EC.1070805@eaglescrag.net>
"J.H." <warthog19@eaglescrag.net> 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
next prev parent reply other threads:[~2009-01-10 1:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 4:25 [PATCH] gitweb: support the rel=vcs microformat Joey Hess
2009-01-07 12:30 ` Giuseppe Bilotta
2009-01-07 15:50 ` Joey Hess
2009-01-07 18:03 ` Giuseppe Bilotta
2009-01-07 18:41 ` Joey Hess
2009-01-10 0:01 ` Jakub Narebski
2009-01-07 18:45 ` Joey Hess
2009-01-07 19:02 ` Joey Hess
2009-01-07 23:24 ` [PATCH] gitweb: support the rel=vcs-* microformat Joey Hess
2009-01-08 7:56 ` Giuseppe Bilotta
2009-01-08 19:54 ` gitweb index performance (Re: [PATCH] gitweb: support the rel=vcs-* microformat) Joey Hess
2009-01-08 23:53 ` J.H.
2009-01-09 0:16 ` Miklos Vajna
2009-01-09 0:19 ` Johannes Schindelin
2009-01-09 0:26 ` J.H.
2009-01-10 1:44 ` Jakub Narebski [this message]
2009-01-10 1:11 ` Jakub Narebski
2009-01-10 1:04 ` [PATCH] gitweb: support the rel=vcs-* microformat Jakub Narebski
2009-01-10 0:52 ` Jakub Narebski
2009-01-10 0:03 ` [PATCH] gitweb: support the rel=vcs microformat Jakub Narebski
2009-01-09 23:56 ` Jakub Narebski
2009-01-09 23:49 ` 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=m3y6xkylwu.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=giuseppe.bilotta@gmail.com \
--cc=joey@kitenet.net \
--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).