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:56:36 +0200 [thread overview]
Message-ID: <ebcm1j$6gi$1@sea.gmane.org> (raw)
In-Reply-To: ebcivb$t6m$1@sea.gmane.org
Jakub Narebski wrote:
> 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
Adding "--remove-empty" (would this change output for git_history much?)
changes this to:
Requests per second: 0.75 [#/sec] (mean)
Time per request: 1341.702 [ms] (mean)
Time per request: 1341.702 [ms] (mean, across all concurrent requests)
Transfer rate: 17.37 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.0 0 0
Processing: 1208 1340 206.6 1241 1729
Waiting: 386 408 36.6 403 510
Total: 1208 1340 206.6 1241 1729
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-08-09 12:57 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
2006-08-09 12:56 ` Jakub Narebski [this message]
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='ebcm1j$6gi$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).