[darcs-users] hashed-storage index

[Trent W. Buck]

Eric Kow <kowey at darcs.net> writes:

> On Sun, Jun 07, 2009 at 11:32:12 +0200, Petr Rockai wrote:
>>> Will loading/reading a 7.2M file for darcs operations create any
>>> noticeable overhead?
>>
>> Well, what do you mean with "noticeable overhead" anyway?
>
> I just meant if reading the large index file would contribute a
> significant amount (say a few seconds) of time to our total wall time
> in a large repository (as you say, it's still a net improvement, but
> I'm just curious).

Pathological example: I have a file with a large number of changed
files.  One of these, "foo", has grown from an empty file to a one-line
file.

If I run "darcs whatsnew foo", i.e. restricting the whatsnew check to
that single file, will it take noticably longer to read foo *and* the
huge index (with hashed-storage) as compared to just reading foo (which,
theoretically, is what Darcs 2.2 does)?