| commit | 90c6cebc43212acca29b5e4e840ef906aa07657b | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Tue, 5 Aug 2008 02:40:57 +0000 (4 19:40 -0700) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Tue, 5 Aug 2008 02:40:57 +0000 (4 19:40 -0700) | ||
| tree | 9fdec791a90023f6d74630becc62a5e319981584 | treesnapshot (tar.gz zip) |
| parent | ab5fea48e98103d00b68807b81e8ac3cb21559cc | commitdiff |
Remove the "jgit is slow" remark from README
Historically this may have been true, back when we built things
on the lib.Commit and lib.Tree API. Those APIs are quickly being
rebuilt around RevWalk and TreeWalk, which are much more powerful
and significantly faster.
Most testing indicates that once the JIT has had a chance to do
its optimization magic on the jgit library we get performance that
really does rival C git running on the same system. Since C git
is so ridiculously fast we're probably still beating many of the
other VCS tools available.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Historically this may have been true, back when we built things
on the lib.Commit and lib.Tree API. Those APIs are quickly being
rebuilt around RevWalk and TreeWalk, which are much more powerful
and significantly faster.
Most testing indicates that once the JIT has had a chance to do
its optimization magic on the jgit library we get performance that
really does rival C git running on the same system. Since C git
is so ridiculously fast we're probably still beating many of the
other VCS tools available.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| README | diffblobblamehistory |