Nicolas Pitre ed4a9031ea pack-objects: allow for early delta deflating
When the delta data is cached in memory until it is written to a pack
file on disk, it is best to compress it right away in find_deltas() for
the following reasons:

  - we have to compress that data anyway;

  - this allows for caching more deltas with the same cache size limit;

  - compression is potentially threaded.

This last point is especially relevant for SMP run time.  For example,
repacking the Linux repo on a quad core processor using 4 threads with
all default settings produce the following results before this change:

	real    2m27.929s
	user    4m36.492s
	sys     0m3.091s

And with this change applied:

	real    2m13.787s
	user    4m37.486s
	sys     0m3.159s

So the actual execution time stayed more or less the same but the
wall clock time is shorter.

This is however not a good thing to do when generating a pack for
network transmission.  In that case, the network is most likely to
throttle the data throughput, so it is best to make find_deltas()
faster in order to start writing data ASAP since we can afford
spending more time between writes to compress the data
at that point.

Signed-off-by: Nicolas Pitre <nico@cam.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2008-05-03 18:35:38 -07:00
2007-06-07 00:04:01 -07:00
2008-04-04 22:38:32 -07:00
2008-04-22 00:10:20 -07:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2008-02-29 00:00:09 -08:00
2007-05-30 15:03:50 -07:00
2007-06-07 00:04:01 -07:00
2008-04-16 00:45:52 -07:00
2008-02-27 13:03:50 -08:00
2008-04-27 21:47:51 -07:00
2008-04-19 21:09:54 -07:00
2008-02-27 13:03:50 -08:00
2007-11-09 00:21:44 -08:00
2008-03-14 00:16:42 -07:00
2008-03-14 00:16:42 -07:00
2008-04-24 22:40:02 -07:00
2008-02-26 00:14:22 -08:00
2008-03-02 23:59:50 -08:00
2008-01-16 15:35:35 -08:00
2008-03-26 00:10:55 -07:00
2008-03-01 01:51:44 -08:00
2008-04-13 12:11:11 -07:00
2008-02-16 17:59:20 -08:00
2007-06-07 00:04:01 -07:00
2008-04-09 01:25:28 -07:00
2007-06-07 00:04:01 -07:00
2008-04-09 01:09:12 -07:00
2008-02-05 00:46:49 -08:00
2008-02-27 13:02:57 -08:00
2008-03-05 10:32:01 -08:00
2008-02-25 23:57:35 -08:00
2008-04-16 00:45:52 -07:00
2008-04-02 00:22:20 -07:00
2008-04-19 21:11:29 -07:00
2008-04-07 21:57:43 -07:00
2008-04-29 23:11:57 -07:00
2008-04-01 23:40:06 -07:00
2008-02-27 15:37:57 -08:00
2008-02-05 23:31:17 -08:00
2008-03-15 00:09:33 -07:00
2007-12-13 23:04:26 -08:00
2008-02-09 23:16:51 -08:00
2008-02-25 23:57:35 -08:00
2007-06-07 00:04:01 -07:00
2007-11-02 16:27:37 -07:00
2007-11-02 16:27:37 -07:00
2008-02-17 12:47:01 -08:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2008-03-08 21:29:56 -08:00
2008-04-20 16:03:40 -07:00
2007-11-09 21:14:10 -08:00
2008-02-25 19:57:06 -08:00
2008-03-02 15:11:07 -08:00
2007-05-01 02:59:08 -07:00
2008-03-02 15:11:07 -08:00
2008-02-25 23:57:35 -08:00
2008-02-27 15:37:57 -08:00
2008-03-14 00:16:42 -07: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.
It was originally written by Linus Torvalds with help of a group of
hackers around the net. It is currently maintained by Junio C Hamano.

Please read the file INSTALL for installation instructions.
See Documentation/tutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands,
and "man git-commandname" for documentation of each command.
CVS users may also want to read Documentation/cvs-migration.txt.

Many Git online resources are accessible from http://git.or.cz/
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. 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://marc.theaimsgroup.com/?l=git and other archival sites.

The messages titled "A note from the maintainer", "What's in
git.git (stable)" and "What's cooking in git.git (topics)" and
the discussion following them on the mailing list give a good
reference for project status, development direction and
remaining tasks.
Description
No description provided
Readme 235 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%