From: Pierre Ossman <ossman@cendio.se>
To: Patrick Steinhardt <ps@pks.im>
Cc: Han Young <hanyang.tony@bytedance.com>, git@vger.kernel.org
Subject: Re: [External] git keeps recreating packs, exploding backup increments
Date: Fri, 9 May 2025 12:27:47 +0200 [thread overview]
Message-ID: <0f0a0dc6-2223-4d59-bc9e-5c8ebfbff09e@cendio.se> (raw)
In-Reply-To: <b0b1007c-34a6-4e3f-9982-cfe617affe1a@cendio.se>
Following up on this old thread.
I think the entire thing might be a false diagnostic on our part, and
git's default behaviour is working just fine for us.
We initially starting looking at this because the backups exploded in
size. But git is complex enough that we had a hard time examining things
retroactively. Instead, we started monitoring things going forward to
find likely causes.
What we did was to keep an eye on how new the files were in
.git/objects/pack. And we kept seeing that the large packs were brand
spanking new. Hence, the attempts at reconfiguring git, and the thread here.
But it seems we didn't look close enough. Although the timestamps
suggest that the packs are constantly being modified, the names and
contents actually stay the same.
I've been keeping a closer eye on a couple of active repositories, and
we aren't actually seeing any excessive growth in size. But the largest
pack files always have a very current modification time.
No idea what caused that initial spike in backup storage. We'll have to
revisit that if it happens again.
Regards,
--
Pierre Ossman Software Development
Cendio AB https://cendio.com
Teknikringen 8 https://twitter.com/ThinLinc
583 30 Linköping https://facebook.com/ThinLinc
Phone: +46-13-214600
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
next prev parent reply other threads:[~2025-05-09 10:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 9:38 git keeps recreating packs, exploding backup increments Pierre Ossman
2025-02-20 3:03 ` [External] " Han Young
2025-02-20 8:26 ` Pierre Ossman
2025-02-21 8:16 ` Patrick Steinhardt
2025-02-24 9:10 ` Pierre Ossman
2025-05-09 10:27 ` Pierre Ossman [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-11 18:03 OryAkerbay
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=0f0a0dc6-2223-4d59-bc9e-5c8ebfbff09e@cendio.se \
--to=ossman@cendio.se \
--cc=git@vger.kernel.org \
--cc=hanyang.tony@bytedance.com \
--cc=ps@pks.im \
/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).