From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: jgit performance update
Date: Sun, 03 Dec 2006 15:19:36 +0100 [thread overview]
Message-ID: <ekumdo$imo$1@sea.gmane.org> (raw)
In-Reply-To: 200612031455.48032.robin.rosenberg.lists@dewire.com
Robin Rosenberg wrote:
> söndag 03 december 2006 05:59 skrev Shawn Pearce:
>
>> With the help of Robin Rosenberg I've been able to make jgit's log
>> operation run (on average) within a few milliseconds of core Git.
>>
>> Walking the 50,000 most recent commits from the Mozilla trunk[1]:
>>
>> $ time git rev-list --max-count=50000 HEAD >/dev/null
>>
>> core Git: 1.882s (average)
>> jgit: 1.932s (average)
>>
>> (times are with hot cache and from repeated executions)
> Nice indeed. That was a ten-fold improvement for getting my full history.
>
> So, just go on to the next case. I added filtering on filenames (yes,
> CVS-induced brain damage, I should track the content. next version. filenames
> are so much handier to work with).
Git uses <path> as _revision limiter_, not as output filter. Shouldn't
jgit do the same?
P.S. What is the status of --follow option?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-12-03 14:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-03 4:59 jgit performance update Shawn Pearce
2006-12-03 13:55 ` Robin Rosenberg
2006-12-03 14:19 ` Jakub Narebski [this message]
2006-12-03 15:53 ` Robin Rosenberg
2006-12-03 23:06 ` Shawn Pearce
2006-12-03 22:59 ` Shawn Pearce
2006-12-03 17:45 ` Linus Torvalds
2006-12-03 17:56 ` Jakub Narebski
2006-12-03 22:42 ` Juergen Stuber
2006-12-03 23:39 ` Robin Rosenberg
2006-12-03 23:58 ` Jakub Narebski
2006-12-04 0:46 ` Shawn Pearce
2006-12-04 20:35 ` Juergen Stuber
2006-12-03 22:47 ` Shawn Pearce
2006-12-03 21:55 ` sf
2006-12-03 22:16 ` Shawn Pearce
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='ekumdo$imo$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).