From: Laurent Alebarde <l.alebarde@free.fr>
Subject: Is Git multithreaded ?
Date: Wed, 12 Jun 2013 20:28:52 +0200
Message-ID: <51B8BDE4.7030008@free.fr>
References: <51B8BBC0.6020908@free.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
To: git@vger.kernel.org
Envelope-to: gcvg-git-2@plane.gmane.org
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130513 Thunderbird/17.0.5
In-Reply-To: <51B8BBC0.6020908@free.fr>
Sender: git-owner@vger.kernel.org
Precedence: bulk
Archived-At: <http://permalink.gmane.org/gmane.comp.version-control.git/227662>

Hi list,

I wonder if Git is multithreaded ? For example, during a commit, does it 
process the files one after one, or does it use a set of threads, say 
10, to process 10 files in parrallel ?

In the Git_Guide (http://wiki.sourcemage.org/Git_Guide.html), I can read 
this :

"T/o enable aut-detection for number of threads to use (good for 
multi-CPU or multi-core computers) for packing repositories, use: /////

////

///$ git config --global pack.threads "0"/  "

But it is not a lot explanatory (to me). In particular, if Git is 
multithreded and can be configured regarding the number of workers, I 
wonder in which operations it uses it ?

A clear view of this may be of interrest for hooks or filters that may 
use a daemon, in order to not have this daemon be a bottle-neck. It 
would make sense to start as many workers in the daemon that there are 
authorized ones in Git.

Cheers,


Laurent.