Re: git-merge-cache / StGIT - gitmergeonefile.py: merging one tree into another rather than two trees into merge base

From: Blaisorblade <blaisorblade@yahoo.it>
Date: Sep 14, 2005, 17:46 UTC
Message-ID: <200509141946.35002.blaisorblade@yahoo.it>
In-Reply-To: <43257BB3.5020506@citi.umich.edu>

On Monday 12 September 2005 14:59, Chuck Lever wrote:

> Catalin Marinas wrote:
> > On Sat, 2005-09-10 at 20:27 +0200, Blaisorblade wrote:

> >>Today I was pushing my patch stack (which was against Linux 2.6.13) on
> >> top of the latest snapshot I have (i.e. upstream will likely have some
> >> mega of patches). And it was *really* slow (say it pushed 8 patches in 5
> >> minutes).

> > That's indeed very slow. How may files are modified in each patch? Do
> > you run it over NFS? Also for profiling, it is useful to run a 'stg
> > status' just to warm up the cache a little bit.

> i've probably seen similar behavior with git-update-index, but i never
> bothered to measure it.  blaisorblade, how are you profiling git?

I'm not, I just did the "testing" (actually I was simply using StGIT) I noticed and reported this behaviour (I even had time to run top to watch what was happening).

As said in the other answer, yes, I verified that it wasn't only for time spent getting cache-hot, and I'm not running on NFS, nor running big things in background.

-- 
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade

	

	
		
___________________________________ 
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB 
http://mail.yahoo.it