git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Kousik Sanagavarapu <five231003@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Running out of inodes on an NFS which stores repos
Date: Tue, 9 Sep 2025 00:29:21 +0000	[thread overview]
Message-ID: <aL904XGUmXmnyXGl@fruit.crustytoothpaste.net> (raw)
In-Reply-To: <DCN87S14V9G8.3BAV5XX1BDHKM@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 930 bytes --]

On 2025-09-08 at 07:05:08, Kousik Sanagavarapu wrote:
> Yes, I have now set the following config surrounding gc
> 
> 	[receive]
> 		autogc = true
> 	[gc]
> 		auto = 1
> 		autopacklimit = 1
> 
> Curious to know if this will have any noticable performance impact
> though. As I mentioned in my previous msg, these are small repos but the
> number of repos being created and the operations performed on them are
> large - mostly pushes,

The `transfer.unpackLimit` will not have any impact; it's in use at at
least some major forges.  Packed objects can use things like bitmaps and
other functionality, which forges like for performance.

The gc settings you have will cause everything to repacked after every
push, and repacking data can be quite expensive.  At work, we repack
after about every 40 pushes or so.  You may wish to use a different
value.
-- 
brian m. carlson (they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2025-09-09  0:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-06 14:16 Running out of inodes on an NFS which stores repos Kousik Sanagavarapu
2025-09-06 15:28 ` rsbecker
2025-09-06 15:34 ` brian m. carlson
2025-09-08  7:05   ` Kousik Sanagavarapu
2025-09-09  0:29     ` brian m. carlson [this message]
2025-09-09  7:39       ` Kousik Sanagavarapu

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=aL904XGUmXmnyXGl@fruit.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=five231003@gmail.com \
    --cc=git@vger.kernel.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).