Re: Something is broken in repack
- From
Jon Smirl <jonsmirl@gmail.com>
- Date
- Dec 11, 2007, 06:20 UTC
- Message-ID
- <9e4733910712102220u47601845q60ccfd754e71936b@mail.gmail.com>
- In-Reply-To
- <BAYC1-PASMTP08CFB6F824B1282649E5EAAE640@CEZ.ICE>
On 12/11/07, Sean <seanlkml@sympatico.ca> wrote:
Show 20 quoted lines
> On Tue, 11 Dec 2007 00:25:55 -0500 > "Jon Smirl" <jonsmirl@gmail.com> wrote: > > > Something is hurting bad with threads. 170 CPU minutes with one > > thread, versus 195 CPU minutes with four threads. > > > > Is there a different memory allocator that can be used when > > multithreaded on gcc? This whole problem may be coming from the memory > > allocation function. git is hardly interacting at all on the thread > > level so it's likely a problem in the C run-time. > > You might want to try Google's malloc, it's basically a drop in replacement > with some optional built-in performance monitoring capabilities. It is said > to be much faster and better at threading than glibc's: > > http://code.google.com/p/google-perftools/wiki/GooglePerformanceTools > http://google-perftools.googlecode.com/svn/trunk/doc/tcmalloc.html > > > You can LD_PRELOAD it or link directly.
I'm 45 minutes into a run using it. It doesn't seem to be any faster but it is reducing memory consumption significantly. The run should be done in another 20 minutes or so.
> > Cheers, > Sean >
-- Jon Smirl jonsmirl@gmail.com