Hey, On Thu, Mar 10, 2011 at 9:27 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > How big a performance penalty does libgit2 have to pay to depart from many > "we run once and let exit take care of cleaning up after us" patterns used > in git.git primarily in order to avoid the housekeeping cost? It's not significant. We try to use custom memory allocation wherever possible, and the most complex structures (interdependencies in parsed objects from the DAG) are internally garbage collected, so we don't do any unnecessary free's. We try to offset the cost of 'proper' memory management by using smarter/more performance tuned algorithms. So far, some stuff ranges from varying degrees of faster-than-git (see: new revision walker, index writing, streaming loose object writes) to slightly slower (see object parsing :/). We are working on it. Performance is our main concern. Cheers, Vicent -- 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