On Sun, Mar 16, 2014 at 08:35:04PM +0700, Nguyễn Thái Ngọc Duy wrote: > As explained in the previous commit, current aggressive settings > --depth=250 --window=250 could slow down repository access > significantly. Notice that people usually work on recent history only, > we could keep recent history more loosely packed, so that repo access > is fast most of the time while the pack file remains small. One thing I have not seen is real-world timings showing the slowdown based on --depth. Did I miss them, or are we just making assumptions based on one old case from 2009 (that, AFAIK does not have real numbers, just speculation)? Has anyone measured the effect of bumping the delta cache size (and its hash implementation)? > git.git is not a great repo to test it because its size is modest but > so are my laptop's cpu and memory, so here are the timings and pack > sizes > > size time > old aggr. 36MB 5m51 > new aggr. 37MB 6m13 > repack -adf 48MB 1m12 I am not clear on what these times mean. It looks like the new code is slower _and_ bigger. Can you explain them? -Peff -- 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