From: Nicolas Pitre <nico@cam.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] change the unpack limit threshold to a saner value
Date: Wed, 06 Dec 2006 19:19:41 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0612061915240.2630@xanadu.home> (raw)
In-Reply-To: <7vejrcy860.fsf@assigned-by-dhcp.cox.net>
On Wed, 6 Dec 2006, Junio C Hamano wrote:
> Nicolas Pitre <nico@cam.org> writes:
>
> > Let's assume the average object size is x. Given n objects, the needed
> > storage size is n*(x + b), where b is the average wasted block size on
> > disk.
> > ...
> > This is why I think the current default treshold should be 3 instead of
> > the insane value of 5000. But since it feels a bit odd to go from 5000
> > to 3 I setled on 10.
>
> I see you are optimizing for disk footprint, and this will
> result in tons of tiny packs left between "repack -a".
Depends how often i.e. how big pushes are, and how often you repack.
> I have not benched it yet, but the runtime pack handling code
> was written assuming we have only a handful of big packs; I
> suspect this change would affect the performance at runtime in
> quite a bad way.
Possibly.
Still a treshold of 5000 is way too large IMHO.
next prev parent reply other threads:[~2006-12-07 0:19 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 [this message]
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
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.0612061915240.2630@xanadu.home \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).