Johannes Schindelin e4621a0169 packfile: fix perf regression with many packs
Since 589127caa7 (packfile: move list of packs into the packfile
store, 2025-10-30), there is a performance regression when many
packfiles need to be loaded: `packfile_store_add_pack()` now calls
`packfile_list_remove_internal()` to detect whether the packfile was
_already_ in the list, and if so, move it to the end of the list. This
function linearly scans the existing list before every insertion. Newly
loading N packs therefore has complexity O(N²).

In one reported use case (https://github.com/microsoft/git/issues/970),
N equals 37,815 and caused a slow-down of a simple `git rev-parse
--short HEAD` (which is regularly executed as part of `GIT_PS1`) from
0.4s to 4.5s.

Let's fix this by establishing a fast path for known-new packfiles.

The keen reader will note that there is currently only a single,
"known-new" caller of the `packfile_list_append()` function, and wonder
why not simply remove this check whether the packfile already exists in
the list? Originally, when above-mentioned commit introduced that logic,
there was a second caller in `prepare_midx()`, which would have required
that check, but that caller was removed in 6aff1f25a0 (packfile:
always add packfiles to MRU when adding a pack, 2025-10-30). Still, the
function is declared in a header file, and to avoid any problems with
in-flight or downstream callers, it is safer to extend the signature to
be explicit whether or not to skip that check.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2026-08-13 09:45:46 -07:00
2026-06-22 20:05:03 -07:00
2026-06-16 09:01:03 -07:00
2026-07-06 15:50:25 -07:00
…
…
…
2026-04-09 17:25:36 -07:00
2026-05-21 12:06:48 +09:00
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
2026-03-23 09:20:29 -07:00
…
…
…
…
2026-05-21 12:06:48 +09:00
…
…
…
…
…
2026-06-08 00:21:35 +09:00
2026-06-15 07:41:59 -07:00
…
…
…
…
2026-05-30 07:07:27 +09:00
…
2026-06-05 22:27:24 +09:00
…
2026-05-30 07:07:27 +09:00
2026-05-30 07:07:27 +09:00
…
…
…
2026-03-23 08:33:10 -07:00
…
…
…
2026-07-06 15:50:25 -07:00
2026-06-18 09:46:56 -07:00
…
…
…
…
…
…
…
…
2026-05-14 15:59:25 +09:00
2026-05-14 15:59:25 +09:00
2026-06-15 07:42:00 -07:00
2026-06-28 15:18:24 -07:00
…
…
…
…
…
…
…
2026-06-11 04:31:17 -07:00
…
…
…
…
2026-07-06 15:50:21 -07:00
…
…
2026-06-15 07:42:00 -07:00
…
…
…
…
…
2026-05-15 04:50:45 +09:00
2026-05-15 04:50:45 +09:00
2026-07-06 15:50:21 -07:00
…
2026-05-30 07:07:27 +09:00
2026-07-06 15:50:23 -07:00
2026-06-09 10:04:50 +09:00
…
…
…
2026-05-19 12:14:03 +09:00
2026-05-19 12:14:03 +09:00
…
…
…
…
2026-03-23 21:27:17 -07:00
…
2026-07-06 15:50:25 -07:00
2026-06-07 23:58:24 +09:00
2026-06-05 22:27:24 +09:00
…
…
…
…
…
2026-07-06 15:50:24 -07:00
2026-06-09 10:04:50 +09:00
…
…
2026-06-09 10:04:50 +09:00
2026-05-13 00:48:42 +09:00
…
…
…
…
…
…
…
…
…
…
…
2026-05-30 07:07:27 +09:00
…
…
…
…
…
…
…
…
2026-03-31 20:43:14 -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.adoc to get started, then see Documentation/giteveryday.adoc for a useful minimum set of commands, and Documentation/git-<commandname>.adoc 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.adoc (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 and Documentation/CodingGuidelines).

Those wishing to help with error message, usage and informational message string translations (localization l10) should see po/README.md (a po file is a Portable Object file that holds the translations).

To subscribe to the list, send an email to git+subscribe@vger.kernel.org (see https://subspace.kernel.org/subscribing.html for details). The mailing list archives are available at https://lore.kernel.org/git/, https://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
Languages
C 49.8%
Shell 39.8%
Perl 4.3%
Tcl 3%
Python 0.8%
Other 2.1%