Juliusz:
the initial commit was about that size. After that there were many small
commits, that worked fine, but at some moment something happened.
Basically, it was one commit that caused the trouble. I'm ready to
accept the fact that there may be such situations with DARCS. The
problem is that although it is known that there may be such situations,
DARCS does not provide any clues what causes them (yes, I've seen about
150 'mergers' after one commit, that became 300 after the next, that
became 500 after the next).
Again, my point is that DARCS probably 'knows' internally that something
goes wrong (that causes this exponential growth of execution time), but
it does not provide any information that would help to solve the problem
manually. And, it is extremely important to have an estimate of how long
will it take to actually resolve interdependencies, given that it
already takes very long time - I can wait (in some situations) 2 hours,
or even 24 hours, but it may take a month or a year to complete - we all
understand what the exponent really is, do we?
Regards,
Valentyn.
Juliusz Chroboczek wrote:
I was trying to use darcs for a 50Mb project, and after 20+ commits
it started to be extremely slow. The last message that I see on the
screen before it goes into Nirvana is 'diffing dir...'
Are you actually committing 50MB in a single record? You'll get
better performance by making smaller commits (having a large tree is
okay, but Darcs is certainly not optimised for very large imports.)
Are you storing autogenerated files? Are they marked binary? What
does ``darcs resolve'' say?
How much physical memory do you have?
Juliusz
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
