[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [jgit-dev] Smudged Index Update Performance
- From: Markus Duft <markus.duft@xxxxxxxxxx>
- Date: Thu, 05 Jul 2012 11:31:23 +0200
- Delivered-to: email@example.com
- Organization: Salomon Automation GmbH
- User-agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120625 Thunderbird/13.0
Ah, i didn't fill out the numbers... sorry;
The updating takes 435 of 457 seconds. thats ~95% of the whole runtime.
On 07/05/2012 11:29 AM, Markus Duft wrote:
> I noticed that since i last updated our JGit tree, all merge operations (merge, rebase, cherry-pick) are quite slow on our big repository. I asked the profiler (JProfiler) for his opinion, and he told me that DirCache.updateSmudgedEntries() eats up ??? seconds of the ??? seconds the cherry-pick took in whole (ofc it's slower because of the profiler, but the relation should be ok...). thats a whopping ?? percent!
> Any suggestions? AFAICT the problem is that each BaseDirCacheEditor.commit() call will cause a write() on the cache, causing the updating to happen. It now depends (really?) on the number of merged files how often /all/ index entries are checked for smudging. Not so cool. I will have a look into making the update an explicit call that happens further up the call tree only once after finishing the merge, or something like that.
> jgit-dev mailing list