[darcs-users] Large initial sets

Ivan Stankovic pokemon at fly.srk.fer.hr
Fri Aug 27 10:10:48 UTC 2004


On Fri, Aug 27, 2004 at 06:33:32AM -0400, David Roundy wrote:
> On Thu, Aug 26, 2004 at 04:16:41PM +0200, Ivan Stankovic wrote:
> > Sorry for being ignorant, but does this mean that using --adds-only would
> > only avoid commuting patches (while all of them would be present in the
> > memory anyway)?  If so, I don't see any great benefits of doing that;
> > yes, it would certainly help, but still having to load the entire
> > (potentially huge) repo would be a pain.
> 
> The point would be that the commuting and reordering of patches is what
> requires the entire repo to be in memory.  Without that, the patch could be
> built lazily without being stored in memory.

Ah, I get it now.  Thanks for the clarification.

> > > Breaking an initial patch into multiple patches, while possible, is an
> > > awfully ugly hack that I'd rather leave to the user.  It should be possible
> > > to reduce memory use on the initial record to a reasonable level--that is
> > > to say, to less than or equal to the memory used by darcs get on the same
> > > patch.  Currently it's something like 50% higher than the memory used by
> > > darcs get.
> > 
> > The possibility sounds nice; I think ideal initial darcs record should take
> > no longer than time needed to copy the whole repo plus some relatively small
> > constant.
> 
> Well, every file still needs to be parsed, so it'll be some constant
> *times* the time needed to copy the repo.

Right, so you just need to make that constant pretty close to 1.  :-)
-- 
Ivan Stankovic, pokemon at fly.srk.fer.hr




More information about the darcs-users mailing list