Re: Something is broken in repack

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 11 Dec 2007 00:25:55 -0500
"Jon Smirl" <jonsmirl@xxxxxxxxx> 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.

Cheers,
Sean
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux