Derrick Stolee 45f4eeb291 pack-bitmap-write: relax unique revwalk condition
The previous commits improved the bitmap computation process for very
long, linear histories with many refs by removing quadratic growth in
how many objects were walked. The strategy of computing "intermediate
commits" using bitmasks for which refs can reach those commits
partitioned the poset of reachable objects so each part could be walked
exactly once. This was effective for linear histories.

However, there was a (significant) drawback: wide histories with many
refs had an explosion of memory costs to compute the commit bitmasks
during the exploration that discovers these intermediate commits. Since
these wide histories are unlikely to repeat walking objects, the benefit
of walking objects multiple times was not expensive before. But now, the
commit walk *before computing bitmaps* is incredibly expensive.

In an effort to discover a happy medium, this change reduces the walk
for intermediate commits to only the first-parent history. This focuses
the walk on how the histories converge, which still has significant
reduction in repeat object walks. It is still possible to create
quadratic behavior in this version, but it is probably less likely in
realistic data shapes.

Here is some data taken on a fresh clone of the kernel:

             |   runtime (sec)    |   peak heap (GB)   |
             |                    |                    |
             |   from  |   with   |   from  |   with   |
             | scratch | existing | scratch | existing |
  -----------+---------+----------+---------+-----------
    original |  64.044 |   83.241 |   2.088 |    2.194 |
  last patch |  45.049 |   37.624 |   2.267 |    2.334 |
  this patch |  88.478 |   53.218 |   2.157 |    2.224 |

Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
Helped-by: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Signed-off-by: Taylor Blau <me@ttaylorr.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2020-12-08 14:49:07 -08:00
2020-11-11 13:18:40 -08:00
2020-12-08 14:48:16 -08:00
2020-11-09 14:06:25 -08:00
2020-09-22 12:36:28 -07:00
2020-08-13 11:02:15 -07:00
2020-10-05 14:01:52 -07:00
2020-03-05 10:43:02 -08:00
2020-07-30 19:18:06 -07:00
2019-09-28 14:04:16 +09:00
2020-09-19 15:56:06 -07:00
2020-09-19 15:56:06 -07:00
2019-11-18 15:21:28 +09:00
2019-11-18 15:21:28 +09:00
2020-04-16 15:38:06 -07:00
2020-09-02 14:39:25 -07:00
2020-09-25 15:25:38 -07:00
2020-08-11 18:04:11 -07:00
2020-08-10 10:23:57 -07:00
2020-08-27 14:04:49 -07:00
2020-11-09 14:06:25 -08:00
2019-12-01 09:04:36 -08:00
2020-08-27 14:04:49 -07:00
2020-07-06 22:09:13 -07:00
2020-08-24 14:54:31 -07:00
2020-07-30 19:18:06 -07:00
2020-11-02 13:17:44 -08:00
2020-11-02 13:17:44 -08:00
2020-11-02 13:17:42 -08:00
2020-08-27 14:04:49 -07:00
2020-07-30 19:18:06 -07:00
2020-07-28 15:02:17 -07:00
2020-09-03 12:37:04 -07:00
2020-09-03 12:37:04 -07:00
2020-03-24 15:04:43 -07:00
2020-08-10 10:23:57 -07:00
2020-11-09 14:06:25 -08:00
2020-11-11 13:18:38 -08:00
2020-10-29 14:24:09 -07:00
2020-07-30 19:18:06 -07:00
2019-11-18 15:21:28 +09:00
2019-11-10 16:00:54 +09:00
2020-07-30 19:18:06 -07:00
2020-06-25 12:27:47 -07:00
2019-11-18 15:21:28 +09:00
2020-07-30 19:18:06 -07:00
2020-07-28 15:02:17 -07:00
2020-11-09 14:06:25 -08:00
2020-10-27 15:09:47 -07:00
2020-05-01 13:39:55 -07:00
2019-12-01 09:04:35 -08:00
2020-08-28 14:07:09 -07:00
2020-07-30 19:18:06 -07:00
2019-12-16 13:08:39 -08:00
2020-07-06 22:09:13 -07:00
2020-03-24 15:04:44 -07:00
2020-03-24 15:04:44 -07:00
2020-07-30 19:18:06 -07:00
2020-10-27 15:09:50 -07:00
2020-10-27 15:09:50 -07:00
2020-10-29 14:24:09 -07:00
2020-10-27 15:09:49 -07:00
2020-10-27 15:09:49 -07:00
2019-11-10 16:00:54 +09:00
2020-04-29 16:15:27 -07:00
2020-09-30 12:53:47 -07:00
2020-07-30 19:18:06 -07:00
2020-07-28 15:02:17 -07:00
2020-08-11 18:04:11 -07:00
2020-08-13 14:13:39 -07:00
2020-09-02 14:39:25 -07:00
2019-11-13 10:09:10 +09:00
2019-11-18 15:21:29 +09:00
2020-07-30 19:18:06 -07:00
2020-07-30 19:18:06 -07:00
2019-09-05 14:10:18 -07:00
2020-07-30 19:18:06 -07:00
2020-07-28 15:02:17 -07:00
2019-11-10 16:00:54 +09:00
2020-11-02 13:17:46 -08:00
2020-10-05 14:01:52 -07:00
2020-10-05 14:01:52 -07:00

Build status

Git - fast, scalable, distributed revision control system

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.

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

See Documentation/gittutorial.txt to get started, then see Documentation/giteveryday.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).

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 https://lore.kernel.org/git/, http://marc.info/?l=git and other archival sites.

Issues which are security relevant should be disclosed privately to the Git Security mailing list git-security@googlegroups.com.

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.

The name "git" was given by Linus Torvalds when he wrote the very first version. He described the tool as "the stupid content tracker" and the name as (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
Description
No description provided
Readme 646 MiB
Languages
C 50.4%
Shell 38.8%
Perl 4.4%
Tcl 3.1%
Python 0.8%
Other 2.3%