On Tue, Apr 21, 2015 at 11:24 PM, Jeff King <p...@peff.net> wrote: > > If I understand correctly, the reason that you need per-run setup is > that your "git clean" command actually cleans things, and you need to > restore the original state for each time-trial. Can you instead use "git > clean -n" to do a dry-run? I think what you are timing is really the > "figure out what to clean" step, and not the cleaning itself. > > -Peff
Yes, that is the problem. A dry run will spot this particular performance issue but maybe we lose some value as a general performance test if we only do "half" the clean? Admittedly we clearly lose some value in the current state as well due to the copying taking more time than the cleaning. I could go either way here. /Erik -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
