On Wed, 20 Apr 2005, Jon Seymour wrote:
> Am I correct to understand that with this change, all the objects in the
> database are still being compressed (so no net performance benefit), but by
> doing the SHA1 calculations before compression you are keeping open the
> possibility that at some point in the future you may use a different
> compression technique (including none at all) for some or all of the
Correct. There is zero performance benefit to this right now, and the only
reason for doing it is because it will allow other things to happen.
Note that the other things include:
- change the compression format to make it cheaper
- _keep_ the same compression format, but notice that we already have an
object by looking at the uncompressed one.
I'm actually leaning towards just #2 at this time. I like how things
compress, and it sure is simple. The fact that we use the equivalent of
"-9" may be expensive, but the thing is, we don't actually write new files
that often, and it's "just" CPU time (no seeking on disk or anything like
that), which tends to get cheaper over time.
So I suspect that once I optimize the tree writing to notice that "oh, I
already have this tree object", and thus build it up but never compressing
it, "write-tree" performance will go up _hugely_ even without removing the
compressioin. Because most of the time, write-tree actually only needs to
create a couple of small new tree objects.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html