Re: [PATCH 0/8] fast-import: cache oe more often
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Sep 20, 2011, 04:02 UTC
- Message-ID
- <7vy5xj7tf5.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <1316395657-6991-1-git-send-email-divanorama@gmail.com>
Dmitry Ivankov <divanorama@gmail.com> writes:
Show 12 quoted lines
> fast-import keeps a struct object_entry for each object written to
> it's pack. This is to keep type, pack-coordinates and delta_depth.
> struct object_entry is also used to cache this metadata for objects
> that exist outside fast-import's pack ('old' objects).
> struct object_entry has a small fixed size and thus it should be
> reasonable to cache any 'old' object metadata retrieval to save the
> disk i/o.
>
> Also it is a step toward making fast-import identify objects via
> struct object_entry rather than sha1. One pointer takes less than
> 20 bytes, it'll be later possible to have references to objects
> that don't yet have sha1 computed (fast-import with threads future).I gave the series a cursory look, and the patches all looked like a good and straight forward rewrites. Provided if it is indeed a good idea overall to stuff more objects in-core, that is.
Hopefully people more involved in fast-import can review and ack after the pre-release feature freeze.