git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: 'git gc --aggressive' effectively unusable

From
FPFrans Pop <elendil@planet.nl>
Date
Apr 3, 2010, 23:23 UTC
Message-ID
<201004040123.06877.elendil@planet.nl>
In-Reply-To
<p2gb4087cc51004031433xc57e52bbq733d1d3c5f37f238@mail.gmail.com>
On Saturday 03 April 2010, Michael Witten wrote:
> On Fri, Apr 2, 2010 at 16:05, Frans Pop <elendil@planet.nl> wrote:
> > I haven't had the patience to let it finish
>
> There's your problem.

Yes, I had seen that. But there's a difference between taking much more time and slowing down to such an extend that it never finishes.

I've tried it today on my linux-2.6 repo as well and the same thing happened. At first the progress is not fast but reasonable. When it gets to about 45% percent it starts slowing down a lot: from ~1500 objects per update of the counters to ~300 objects per update. And who knows what the progress is going to be when it reaches 70% or 90%: 10 per update?

With a total of over 2 milion objects in the repository such a low speed is simply not going to work, ever. So I maintain that it is effectively unusable.

Cheers, FJP

Previous: Michael WittenNext: Michael Witten
Message 6 of 13 in “'git gc --aggressive' effectively unusable”
  1. Frans PopApr 2, 2010
  2. Frans PopApr 2, 2010
  3. Frans PopApr 3, 2010
  4. Michael WittenApr 3, 2010
  5. Michael WittenApr 3, 2010
  6. Frans PopApr 3, 2010
  7. Michael WittenApr 3, 2010
  8. Miles BaderApr 4, 2010
  9. Michael PooleApr 4, 2010
  10. Jeff KingApr 4, 2010
  11. Jeff KingApr 4, 2010
  12. Nicolas PitreApr 5, 2010
  13. Mike GalbraithApr 4, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.