From: Linus Torvalds <torvalds@osdl.org>
To: Nicolas Pitre <nico@cam.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] change the unpack limit treshold to a saner value
Date: Wed, 6 Dec 2006 19:39:35 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0612061935250.3615@woody.osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0612062213500.2630@xanadu.home>
On Wed, 6 Dec 2006, Nicolas Pitre wrote:
>
> Note that this setting is currently observed for pushes not pulls.
> On the pull side you currentli need to provide -k for not exploding
> packs.
So noted.
> So the question is what number of objects on average do pushes have? If
> most pushes are below the treshold this is not going to be really
> useful.
It will depend a lot on the project, and "where" in the project you are.
For example, for most end developers, the "push" is likely going to be a
few commits (say, a days work). Probably on the order of a few tens to
maybe a few hundred objects. It's actually hard to create a pack with less
than ten objects if you have a few directory levels (a single small commit
in the kernel is usually 5-7 objects: commit + 2-3 levels of directory + a
couple of blobs).
For me, as I pull a big merge and push it out, a push can easily be in the
thousands of objects, just because I merged other peoples combined work
over several weeks.
And for a "mirror" server, it will depend on the granularity of the
mirroring.
> And I think 5000 is definitely way too high. 10 might be too small
> indeed. 100 is maybe a good default to try out.
I think 100 is a nice round number for humans. Worth trying.
next prev parent reply other threads:[~2006-12-07 3:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 21:08 [PATCH] change the unpack limit treshold to a saner value Nicolas Pitre
2006-12-06 22:24 ` [PATCH] change the unpack limit threshold " Junio C Hamano
2006-12-07 0:19 ` Nicolas Pitre
2006-12-07 1:08 ` [PATCH] change the unpack limit treshold " Linus Torvalds
2006-12-07 3:24 ` Nicolas Pitre
2006-12-07 3:39 ` Linus Torvalds [this message]
2006-12-07 4:01 ` [PATCH take 2] " Nicolas Pitre
2006-12-07 7:59 ` Shawn Pearce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0612061935250.3615@woody.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=nico@cam.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).