I have a repo here with about 1300 patches, and darcs record --ask-deps takes
minutes before prompting me for which patches to depend on.

> I have a repo here with about 1300 patches, and darcs record --ask-deps 
> takes minutes before prompting me for which patches to depend on.

After "darcs optimize --checkpoint --compress --modernize-patches
--reorder-patches -v -v -v", it goes much faster -- now it takes only a part of
a minute.  Does this mean that this issue report should be closed?

--Z

Actually I tried this again, and after the optimize step darcs record --ask-deps
*still* takes more than 2 minutes before it prompts me for which patches to
depend on.  So in this test optimize helped not at all.

On Wed, Jan 11, 2006 at 06:57:31PM +0000, Zooko wrote:
> Actually I tried this again, and after the optimize step darcs record
> --ask-deps *still* takes more than 2 minutes before it prompts me for
> which patches to depend on.  So in this test optimize helped not at all.

I think what would help would be to define a tag and then optimize, as
darcs would then only prompt you for patches back to that tag.  This isn't
a complete solution, since it only makes darcs faster by making darcs do
less, but it might be helpful for you.

--ask-deps is inherently a pretty inefficient command.  We could make it
significantly more efficient (especially in startup) by writing custom code
that would be smarter about only looking at patches that might have their
state changed, but that's tricky code to write, and an easy way to
introduce bugs.  Which isn't to say we shouldn't do it, but that it'll take
time, so we shouldn't try to do it unless we've got that time (which I
don't).
-- 
David Roundy
http://www.darcs.net

For me, this looks liks it's "resolved in unstable". On the darcs repo on a 1Ghz
laptop, it took only 5 seconds to bring up this prompt.