Re: Surprising use of memory and time when repacking mozilla's gecko repository

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

 



Mike Hommey <mh@xxxxxxxxxxxx> wrote:
> I'm puzzled by the fact writing objects is so much faster with 1 thread.

I/O contention in the multi-threaded cases?

"public-inbox-index" (reading from git, writing to Xapian+SQLite)
on a dev machine got slow because core count exceeded what SATA
could handle and had to cap the default Xapian shard count to 3
by default for v2 inboxes.


As for memory use, does git use the producer/consumer pattern
for malloc+free so free happens in a different thread from the
malloc?

Because current versions of glibc gets pathological with that case
(but I have a long-term fix for it):

https://public-inbox.org/libc-alpha/20180731084936.g4yw6wnvt677miti@dcvr/T/
Only locklessinc malloc seemed OK in the IPC department
(But I haven't kept up with jemalloc, tcmalloc developments in years)



[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