git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>, git@vger.kernel.org
Subject: Re: There should have be git gc --repack-arguments
Date: Wed, 07 Apr 2021 13:40:16 -0700	[thread overview]
Message-ID: <xmqq8s5tzv4f.fsf@gitster.g> (raw)
In-Reply-To: <YG4J7vtTRVpGGLoo@coredump.intra.peff.net> (Jeff King's message of "Wed, 7 Apr 2021 15:37:18 -0400")

Jeff King <peff@peff.net> writes:

>> ... git repack ...  --max-pack-size=<desired pack size> to create split and
>> smaller packs instead.
> ...
> You can also set pack.packSizeLimit for the latter, though I do not
> recommend it. It will not help with memory usage (neither while
> repacking nor for later commands).

In other words, passing --max-pack-size, whether it is done with a
new --repack-arguments option or it is done with the existing
pack.packSizeLimit configuration, would make things worse.

So in conclusion:

 - attempting to repack everything into one pack on a memory starved
   box would be helped with reduced window memory size.

 - on a small box, it may make sense to avoid repacking everything
   into one in the first place, but we do not want the number of
   packs to grow unbounded.

Would the new geometric repack feature help here, especially for the
latter?


  reply	other threads:[~2021-04-07 20:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07 12:10 There should have be git gc --repack-arguments Bagas Sanjaya
2021-04-07 19:37 ` Jeff King
2021-04-07 20:40   ` Junio C Hamano [this message]
2021-04-07 21:37     ` Jeff King
2021-04-07 22:13       ` Junio C Hamano
2021-04-07 22:22         ` Jeff King
2021-04-09  9:58           ` Bagas Sanjaya
2021-04-09 15:49             ` Jeff King
2021-04-07 19:38 ` Bryan Turner
2021-04-08 13:31   ` Bagas Sanjaya

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq8s5tzv4f.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=bagasdotme@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).