On Friday, September 30, 2011 04:06:31 pm Martin Fick wrote: > > OK, I narrowed it down I believe. If I comment out the > invalidate_cached_refs() line in write_ref_sha1(), it > speeds through this section. > > I guess this makes sense, we invalidate the cache and > have to rebuild it after every new ref is added? > Perhaps a simple fix would be to move the invalidation > right after all the refs are updated? Maybe > write_ref_sha1 could take in a flag to tell it to not > invalidate the cache so that during iterative updates it > could be disabled and then run manually after the > update? Would this solution be acceptable if I submitted a patch to do it? My test shows that this will make a full fetch of ~80K changes go from 4:50min to 1:50min, -Martin -- Employee of Qualcomm Innovation Center, Inc. which is a member of Code Aurora Forum -- 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