* git gc/prune runs again and again
@ 2015-11-03 12:44 Andreas Krey
2015-11-03 15:01 ` Duy Nguyen
0 siblings, 1 reply; 3+ messages in thread
From: Andreas Krey @ 2015-11-03 12:44 UTC (permalink / raw)
To: Git Mailing List
Hi all,
I have a bit of an annoying behaviour in git gc;
there is a repo I regularly do a fetch in, and
this kicks off a gc/prune every time. I remember
there being a heuristic with being that many files
in .git/objects/17 as the gc trigger.
Which is unfortunate if the gc does not actually
reduce the number of files there because they
aren't old enough => gc comes right back.
What can I do there? (This git is a bit old, 2.2.2)
Andreas
--
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: git gc/prune runs again and again
2015-11-03 12:44 git gc/prune runs again and again Andreas Krey
@ 2015-11-03 15:01 ` Duy Nguyen
2015-11-03 15:21 ` Andreas Krey
0 siblings, 1 reply; 3+ messages in thread
From: Duy Nguyen @ 2015-11-03 15:01 UTC (permalink / raw)
To: Andreas Krey; +Cc: Git Mailing List
On Tue, Nov 3, 2015 at 1:44 PM, Andreas Krey <a.krey@gmx.de> wrote:
> Hi all,
>
> I have a bit of an annoying behaviour in git gc;
> there is a repo I regularly do a fetch in, and
> this kicks off a gc/prune every time. I remember
> there being a heuristic with being that many files
> in .git/objects/17 as the gc trigger.
>
> Which is unfortunate if the gc does not actually
> reduce the number of files there because they
> aren't old enough => gc comes right back.
>
> What can I do there? (This git is a bit old, 2.2.2)
Run "git prune". 2.2.2 hides this suggestion to run git-prune in this
case. The next git version will show it back.
--
Duy
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: git gc/prune runs again and again
2015-11-03 15:01 ` Duy Nguyen
@ 2015-11-03 15:21 ` Andreas Krey
0 siblings, 0 replies; 3+ messages in thread
From: Andreas Krey @ 2015-11-03 15:21 UTC (permalink / raw)
To: Duy Nguyen; +Cc: Git Mailing List
On Tue, 03 Nov 2015 16:01:24 +0000, Duy Nguyen wrote:
....
> > I have a bit of an annoying behaviour in git gc;
> > there is a repo I regularly do a fetch in, and
> > this kicks off a gc/prune every time. I remember
> > there being a heuristic with being that many files
> > in .git/objects/17 as the gc trigger.
(It might be a good idea to use a random slot here.)
...
> > What can I do there? (This git is a bit old, 2.2.2)
>
> Run "git prune". 2.2.2 hides this suggestion to run git-prune in this
> case. The next git version will show it back.
Actually, there is a 'git prune --expire 2.weeks.ago --no-progress'
running under the 'git gc --auto --quiet', and I don't want to drop
the expiry time lightly.
Andreas
--
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-11-03 15:43 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-11-03 12:44 git gc/prune runs again and again Andreas Krey
2015-11-03 15:01 ` Duy Nguyen
2015-11-03 15:21 ` Andreas Krey
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox