1
0
mirror of https://github.com/git/git.git synced 2025-03-18 22:48:38 +00:00
Thomas Rast d1b9b76734 Avoid loading commits twice in log with diffs
If you run a log with diffs (such as -p, --raw, --stat etc.) the
current code ends up loading many objects twice.  For example, for
'log -3000 -p' my instrumentation said the objects loaded more than
once are distributed as follows:

  2008 blob
  2103 commit
  2678 tree

Fixing blobs and trees will be harder, because those are really used
within the diff engine and need some form of caching.

However, fixing the commits is easy at least at the band-aid level.
They are triggered by log_tree_diff() invoking diff_tree_sha1() on
commits, which duly loads the specified object to dereference it to a
tree.  Since log_tree_diff() knows that it works with commits and they
must have trees, we can simply pass through the trees.

We add some parse_commit() calls.  The ones for the parents are
required; we do not know at this stage if they have been looked at.
The one for the commit itself is pure paranoia, but has about the same
cost as an assertion on commit->object.parsed.

This has a quite dramatic effect on log --raw, though only a
negligible impact on log -p:

Test                      this tree         HEAD
--------------------------------------------------------------------
4000.2: log --raw -3000   0.50(0.43+0.06)   0.54(0.46+0.06) +7.0%***
4000.3: log -p -3000      2.34(2.20+0.13)   2.37(2.22+0.13) +1.2%
--------------------------------------------------------------------
Significance hints:  '.' 0.1  '*' 0.05  '**' 0.01  '***' 0.001

Signed-off-by: Thomas Rast <trast@student.ethz.ch>
Signed-off-by: Thomas Rast <trast@inf.ethz.ch>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2013-03-28 07:45:21 -07:00
2013-02-26 09:16:58 -08:00
2013-03-11 10:32:16 -07:00
2013-03-27 10:57:57 -07:00
2012-10-17 15:55:46 -07:00
2013-01-18 11:13:22 -08:00
2013-01-30 21:12:16 +11:00
2012-10-25 06:42:02 -04:00
2012-10-25 06:42:02 -04:00
2013-03-01 13:17:18 -08:00
2012-10-29 03:08:30 -04:00
2013-01-23 21:19:10 -08:00
2013-02-04 10:25:04 -08:00
2012-10-29 03:08:30 -04:00
2013-02-26 09:16:58 -08:00
2013-02-17 15:25:52 -08:00
2013-01-23 21:19:10 -08:00
2012-11-28 13:52:54 -08:00
2013-02-04 10:25:30 -08:00
2013-03-13 11:28:08 -07:00
2013-03-11 13:00:16 -07:00
2012-05-03 15:13:31 -07:00
2013-02-11 14:33:04 -08:00
2013-01-20 17:06:53 -08:00
2013-03-17 00:11:11 -07:00
2012-09-11 11:23:54 -07:00
2012-10-17 22:42:40 -07:00
2012-10-29 03:08:30 -04:00
2012-08-03 12:11:07 -07:00
2013-02-05 16:13:32 -08:00
2013-02-17 15:25:57 -08:00
2013-03-25 13:51:13 -07:00
2013-02-04 10:25:04 -08:00
2013-01-20 17:06:53 -08:00
2012-09-18 14:37:46 -07:00
2013-02-27 09:47:28 -08:00
2013-01-16 12:48:22 -08:00
2013-01-16 12:48:22 -08:00
2013-01-23 21:19:10 -08:00
2013-02-17 15:25:57 -08:00

////////////////////////////////////////////////////////////////

	Git - the stupid content tracker

////////////////////////////////////////////////////////////////

"git" can mean anything, depending on your mood.

 - random three-letter combination that is pronounceable, and not
   actually used by any common UNIX command.  The fact that it is a
   mispronunciation of "get" may or may not be relevant.
 - stupid. contemptible and despicable. simple. Take your pick from the
   dictionary of slang.
 - "global information tracker": you're in a good mood, and it actually
   works for you. Angels sing, and a light suddenly fills the room.
 - "goddamn idiotic truckload of sh*t": when it breaks

Git is a fast, scalable, distributed revision control system with an
unusually rich command set that provides both high-level operations
and full access to internals.

Git is an Open Source project covered by the GNU General Public
License version 2 (some parts of it are under different licenses,
compatible with the GPLv2). It was originally written by Linus
Torvalds with help of a group of hackers around the net.

Please read the file INSTALL for installation instructions.

See Documentation/gittutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands, and
Documentation/git-commandname.txt for documentation of each command.
If git has been correctly installed, then the tutorial can also be
read with "man gittutorial" or "git help tutorial", and the
documentation of each command with "man git-commandname" or "git help
commandname".

CVS users may also want to read Documentation/gitcvs-migration.txt
("man gitcvs-migration" or "git help cvs-migration" if git is
installed).

Many Git online resources are accessible from http://git-scm.com/
including full documentation and Git related tools.

The user discussion and development of Git take place on the Git
mailing list -- everyone is welcome to post bug reports, feature
requests, comments and patches to git@vger.kernel.org (read
Documentation/SubmittingPatches for instructions on patch submission).
To subscribe to the list, send an email with just "subscribe git" in
the body to majordomo@vger.kernel.org. The mailing list archives are
available at http://news.gmane.org/gmane.comp.version-control.git/,
http://marc.info/?l=git and other archival sites.

The maintainer frequently sends the "What's cooking" reports that
list the current status of various development topics to the mailing
list.  The discussion following them give a good reference for
project status, development direction and remaining tasks.
Description
Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
Readme 794 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%