Re: performance on repack

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

 



On Wed, 15 Aug 2007, Jon Smirl wrote:

> On 8/15/07, Martin Koegler <mkoegler@xxxxxxxxxxxxxxxxx> wrote:
> > git-pack-objects knows the order, in which it will use the objects.  A
> > seperate thread could pre-read the next object and wait until the main
> > thread starts processing it. After the read is complete, another
> > thread could start computing the delta index.
> 
> The hope is that the new adaptive read ahead code in the kernel will
> get this right and you won't need the second thread. Letting the
> kernel handle the read ahead will dynamically scale as other demands
> are made on the host. There's effectively only one read ahead cache in
> the system, only the kernel really knows how to divide it up between
> competing apps.

No read ahead will ever help the delta search phase.  Objects listed for 
deltification against each other are sorted in a way that results in 
reads from completely random location in the object store.

Normally the delta search phase is so compute intensive that the read 
shouldn't matter much.


Nicolas
-
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