On Tue, Mar 22, 2011 at 01:07:53PM +0100, Michael J Gruber wrote: > I don't get this: > > git cherry A B: 0.4s > git rev-list --cherry A...B: 1.7s > (more details below) > > This makes "rev-list --cherry" almost unacceptable as a replacement. But > I'd like to understand this difference (and maybe do something about > it). I'm lost with gprof, but here are more details on the timing: I don't have much to say on the problem at hand, but have you tried using the "perf" tool from the kernel to measure? These days it ships in linux-tools-2.6.x in Debian unstable; I don't know about other distros. You can do this: perf record git cherry $A $B >/dev/null perf record git rev-list --cherry $A...$B >/dev/null perf diff to get a list of the hot-spots with the time differences between the two runs (along with "perf report" and "perf annotate" to get more information). Disclaimer: I am very new to perf, so I may be misleading you about how useful the "diff" would be. In particular, it seems to be based on a percentages of time spent between two runs. Which is great for two runs of the same program calling very similar functions. But for two programs calling _mostly_ the same functions, I don't know how misleading it is. -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