Basically it's a quick case study (in the form of a mailing list reply) of implementing git in Java, tuning heavily for performance, and comparing to the equally tuned C implementation. Java does well, but fundamental issues like lack of value types (i.e. all objects must go into independently managed heap cells) and memory typesafety (converting a SHA-1 between int[5] and byte[20] is a bounds-checked copy in Java, where it's zero-cost in C) put a firm cap on how fast it can be made to go.
Basically it's a quick case study (in the form of a mailing list reply) of implementing git in Java, tuning heavily for performance, and comparing to the equally tuned C implementation. Java does well, but fundamental issues like lack of value types (i.e. all objects must go into independently managed heap cells) and memory typesafety (converting a SHA-1 between int[5] and byte[20] is a bounds-checked copy in Java, where it's zero-cost in C) put a firm cap on how fast it can be made to go.