Re: 'git gc --aggressive' effectively unusable

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Jeff King
Date: Sunday, April 4, 2010 - 2:49 pm

On Sun, Apr 04, 2010 at 04:38:50PM -0400, Jeff King wrote:


Hmm, this may be relevant:

  http://thread.gmane.org/gmane.comp.version-control.git/67791/focus=94797

In my experiments, memory usage is increasing but valgrind doesn't
leaks. So perhaps it is fragmentation in the memory allocator.

-Peff
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
'git gc --aggressive' effectively unusable, Frans Pop, (Fri Apr 2, 3:05 pm)
Re: 'git gc --aggressive' effectively unusable, Frans Pop, (Sat Apr 3, 2:16 pm)
Re: 'git gc --aggressive' effectively unusable, Michael Witten, (Sat Apr 3, 2:33 pm)
Re: 'git gc --aggressive' effectively unusable, Michael Witten, (Sat Apr 3, 2:42 pm)
Re: 'git gc --aggressive' effectively unusable, Frans Pop, (Sat Apr 3, 4:23 pm)
Re: 'git gc --aggressive' effectively unusable, Michael Witten, (Sat Apr 3, 4:42 pm)
Re: 'git gc --aggressive' effectively unusable, Miles Bader, (Sat Apr 3, 5:14 pm)
Re: 'git gc --aggressive' effectively unusable, Mike Galbraith, (Sat Apr 3, 9:27 pm)
Re: 'git gc --aggressive' effectively unusable, Michael Poole, (Sun Apr 4, 7:50 am)
Re: 'git gc --aggressive' effectively unusable, Jeff King, (Sun Apr 4, 1:38 pm)
Re: 'git gc --aggressive' effectively unusable, Jeff King, (Sun Apr 4, 2:49 pm)
Re: 'git gc --aggressive' effectively unusable, Nicolas Pitre, (Mon Apr 5, 2:07 pm)