Jeff King cd37996795 pack-objects: break out of want_object loop early
When pack-objects collects the list of objects to pack
(either from stdin, or via its internal rev-list), it
filters each one through want_object_in_pack().

This function loops through each existing packfile, looking
for the object. When we find it, we mark the pack/offset
combo for later use. However, we can't just return "yes, we
want it" at that point. If --honor-pack-keep is in effect,
we must keep looking to find it in _all_ packs, to make sure
none of them has a .keep. Likewise, if --local is in effect,
we must make sure it is not present in any non-local pack.

As a result, the sum effort of these calls is effectively
O(nr_objects * nr_packs). In an ordinary repository, we have
only a handful of packs, and this doesn't make a big
difference. But in pathological cases, it can slow the
counting phase to a crawl.

This patch notices the case that we have neither "--local"
nor "--honor-pack-keep" in effect and breaks out of the loop
early, after finding the first instance. Note that our worst
case is still "objects * packs" (i.e., we might find each
object in the last pack we look in), but in practice we will
often break out early. On an "average" repo, my git.git with
8 packs, this shows a modest 2% (a few dozen milliseconds)
improvement in the counting-objects phase of "git
pack-objects --all <foo" (hackily instrumented by sticking
exit(0) right after list_objects).

But in a much more pathological case, it makes a bigger
difference. I ran the same command on a real-world example
with ~9 million objects across 1300 packs. The counting time
dropped from 413s to 45s, an improvement of about 89%.

Note that this patch won't do anything by itself for a
normal "git gc", as it uses both --honor-pack-keep and
--local.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-07-29 11:05:07 -07:00
2016-05-10 11:19:07 -07:00
2016-07-19 13:22:19 -07:00
2016-07-19 13:22:16 -07:00
2016-02-22 14:51:09 -08:00
2016-07-13 11:24:10 -07:00
2016-05-09 12:29:08 -07:00
2016-06-21 11:18:17 -07:00
2016-02-22 14:51:09 -08:00
2016-02-22 14:50:32 -08:00
2016-02-22 14:50:32 -08:00
2016-07-19 13:22:22 -07:00
2015-10-05 12:30:19 -07:00
2016-05-09 12:29:08 -07:00
2016-07-11 10:31:05 -07:00
2016-02-22 14:51:09 -08:00
2016-07-19 13:22:16 -07:00
2015-08-03 11:01:21 -07:00
2016-07-19 13:22:22 -07:00
2016-07-19 13:22:22 -07:00
2016-07-06 13:38:11 -07:00
2016-05-09 12:29:08 -07:00
2016-01-18 19:48:43 -08:00
2016-05-09 12:29:08 -07:00
2014-12-12 14:31:42 -08:00
2016-07-19 13:22:19 -07:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2016-07-19 13:22:16 -07:00
2016-04-03 10:29:22 -07:00
2016-05-23 14:54:29 -07:00
2016-05-23 14:54:29 -07:00
2016-05-09 12:29:08 -07:00
2016-05-09 12:29:08 -07:00
2016-07-19 13:22:19 -07:00
2016-05-17 14:38:34 -07:00
2016-07-01 12:44:57 -07:00
2016-07-01 12:44:57 -07:00
2016-07-19 13:22:24 -07:00
2016-07-15 10:48:16 -07:00
2016-07-01 15:09:10 -07:00
2016-07-19 13:22:15 -07:00
2016-07-19 13:22:17 -07:00
2016-06-28 11:39:02 -07:00
2016-07-06 13:38:06 -07:00
2016-07-06 13:38:06 -07:00
2016-07-19 13:22:19 -07:00
2016-02-22 14:51:09 -08:00
2016-07-19 13:22:16 -07:00
2016-05-17 14:38:32 -07:00
2014-10-20 12:23:48 -07:00
2016-05-17 14:38:28 -07:00
2016-07-29 11:05:07 -07:00
2015-11-20 08:02:05 -05:00
2016-07-29 11:05:07 -07:00
2016-07-29 11:05:07 -07:00
2016-07-19 13:22:16 -07:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2016-07-29 11:05:06 -07:00
2016-05-26 13:17:21 -07:00
2016-07-19 13:22:17 -07:00
2016-07-19 13:22:17 -07:00
2016-05-09 12:29:08 -07:00
2015-09-25 08:54:54 -07:00
2016-07-15 10:48:16 -07:00
2016-05-23 14:54:38 -07:00
2016-04-25 15:17:15 -07:00
2016-07-13 11:24:10 -07:00
2016-05-09 12:29:08 -07:00
2016-05-06 14:45:44 -07:00
2016-07-01 15:09:10 -07:00
2014-12-22 12:27:30 -08:00
2016-07-19 13:22:16 -07:00
2016-07-19 13:22:16 -07:00
2016-07-19 13:22:19 -07:00
2016-02-22 10:40:35 -08:00
2016-07-19 13:22:23 -07:00
2016-07-19 13:22:16 -07:00

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 http://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-.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 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.

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 279 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%