to .d or not to .d

Fri Mar 23 17:13:23 UTC 2007

* TK Soh <teekaysoh at gmail.com> [20070323 16:55]:
> On 3/23/07, Brendan Cully <brendan at kublai.com> wrote:
> >On Friday, 23 March 2007 at 09:49, TK Soh wrote:
> >> I noticed sometime the .d files are not created when I check in new
> >> files. Can someone please share the algorithm used in deciding if/when
> >> a .d file will be created? Thanks.
> >
> >RevlogNG introduced inline data. When the revlog is small, it's faster
> >to slurp up the index in the data in one set of reads (precaching
> >probably grabs it anyway, and you save seeks). When it gets larger - I
> >think above 128K - the data is forked off to keep the index load fast.
> 
> so the data prior to forking will remain in the index file?

No, it gets rewritten in a new location and then moved to the
original location.

Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrück - Registereintrag: Amtsgericht Osnabrück, HR B 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner