From: Shawn Pearce <spearce@spearce.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: jgit performance update
Date: Sun, 3 Dec 2006 17:47:26 -0500 [thread overview]
Message-ID: <20061203224726.GC15965@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0612030938140.3476@woody.osdl.org>
Linus Torvalds <torvalds@osdl.org> wrote:
> Very good. Are we any closer to actually having an eclipse plugin then?
We have some parts in place. But nothing that's user-ready.
> > Walking the 50,000 most recent commits from the Mozilla trunk[1]:
>
> Now, the _interesting_ case in many ways is not "--max-count", but the
> revision limiter. It _should_ be equally fast, but if you've done
> something wrong, it won't be.
We haven't implemented a rev-list equivalent yet. That's a major
feature which is missing. The --max-count test was simple to put
together. I really need to start thinking about replicating some
of the features of the revision functions in core Git.
> > One of the biggest annoyances has been the fact that although Java
> > 1.4 offers a way to mmap a file into the process, the overhead to
> > access that data seems to be far higher than just reading the file
> > content into a very large byte array, especially if we are going
> > to access that file content multiple times.
>
> That must suck for big packed repositories. What JVM and other environment
> are you using?
Mac OS 10.4.8 / Java 1.4.2. It appears as though Sun isn't going
to fix the mmap performance problems as they can't do it "securely".
So its likely to be an issue anywhere jgit gets used...
> Also, I have to say, one of the reasons I'm interested in your project is
> that I've never done any Java programming, because quite frankly, I've
> never had any reason what-so-ever to do so. But if there is some simple
> setup, and you have jgit exposed somewhere as a git archive, I'd love to
> take a look, if only to finally learn more about Java.
Of course its in Git. :-)
There's no webpage here, but you can clone it:
http://www.spearce.org/projects/scm/egit.git
The code you would recognize most is in org.spearce.jgit/.../lib.
E.g. BinaryDelta.java came from patch-delta.c in core Git.
Repository has some of the functionality of sha1_file.c, the pack
reading code is in PackFile.java.
--
next prev parent reply other threads:[~2006-12-03 22:47 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
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 [this message]
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=20061203224726.GC15965@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).