From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH and RFC] gitweb: Remove --full-history from git_history
Date: Wed, 09 Aug 2006 14:04:11 +0200 [thread overview]
Message-ID: <ebcivb$t6m$1@sea.gmane.org> (raw)
In-Reply-To: 7vu04m413f.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>
>> Stop pretending that gitweb is rename-aware, and remove --full-history
>> option to git-rev-list in git_history (for "history" action):
>
> Where did you get the idea that --full-history has anything to
> do with renames?
> Message-ID: <20060701005924.7726.qmail@web31812.mail.mud.yahoo.com>
http://marc.theaimsgroup.com/?l=git&m=115171557714437
> Message-ID: <Pine.LNX.4.64.0606301818480.12404@g5.osdl.org>
http://marc.theaimsgroup.com/?l=git&m=115171683714119
Ooops, sorry, my mistake. Still, even if the patch is to be dropped,
the proposal about rename detection is still valid.
I wonder which version is faster: --full-history, or filter using
diff-tree?
ab -n 10 "http://localhost/cgi-bin/gitweb/gitweb.cgi?p=git.git;a=history;hb=next;f=gitweb/gitweb.perl"
(ApacheBench, Version 2.0.41-dev <$Revision: 1.141 $> apache-2.0) says
Requests per second: 0.09 [#/sec] (mean)
Time per request: 10918.552 [ms] (mean)
Time per request: 10918.552 [ms] (mean, across all concurrent requests)
Transfer rate: 2.13 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.0 0 0
Processing: 8851 10917 2776.1 9284 16420
Waiting: 407 457 95.1 428 721
Total: 8851 10917 2776.1 9284 16420
for --full-history version, and
Requests per second: 0.11 [#/sec] (mean)
Time per request: 9076.865 [ms] (mean)
Time per request: 9076.865 [ms] (mean, across all concurrent requests)
Transfer rate: 2.57 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.0 0 0
Processing: 8741 9076 271.7 9100 9581
Waiting: 299 405 49.5 404 507
Total: 8741 9076 271.7 9100 9581
for the pipe through git-diff-tree version, both with very similar
times (check out median column), although --full-history version
seems slightly slower...
Still, it is ab on workstation, not separate server, an only average
over 10 requests.
And
1025:jnareb@roke:~/git> time git rev-list next -- gitweb/gitweb.perl
[...]
real 0m2.623s
user 0m2.536s
sys 0m0.016s
1024:jnareb@roke:~/git> time git rev-list next | git diff-tree -r --stdin -- gitweb/gitweb.perl
[...]
real 0m6.857s
user 0m6.024s
sys 0m0.068s
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-08-09 12:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 10:57 [PATCH and RFC] gitweb: Remove --full-history from git_history Jakub Narebski
2006-08-09 11:09 ` Junio C Hamano
2006-08-09 12:04 ` Jakub Narebski [this message]
2006-08-09 12:56 ` Jakub Narebski
2006-08-09 19:28 ` Fredrik Kuivinen
2006-08-09 20:08 ` Johannes Schindelin
2006-08-09 21:42 ` Junio C Hamano
2006-08-10 10:46 ` Jakub Narebski
2006-08-10 21:39 ` Fredrik Kuivinen
2006-08-14 11:10 ` 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='ebcivb$t6m$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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).