> I just imported a bunch of files¹ into an existing darcs repository of
> mine. It took a while, and used quite a bit of ram, so I went to the
> darcs website to see if this was normal or something I should report.
This is a known problem with Darcs. Darcs just hates large commits.
We will get around to optimising that case at some point, but it's a
rather low priority.
> Given that the directory I imported weighs in at 75MB and I imported
> it as one patch (one 'darcs record'), maybe I should not be surprised
> that it took more than 5 minutes of cpu-time, taking up 250+MB RAM to
> push it from one 2GHz Pentium 4-box to another, over a LAN.
First of all, you should use |darcs get| or |put| instead of |pull| or
|push|, whenever possible.
250MB seems a little excessive, though -- it should be more like 2
times the size of the commit.
> My question is this: What is the recommended way to import a 75MB
> directory?
If you can, split the repository into multiple repositories. I have
trouble believing that your 75MB are a single project (that's a couple
million lines of code!).
If that is not practical, split the initial import into multiple
records, as suggested on the wiki (2MB seems a little excessive,
though, for an initial commit; it's a good guideline for later
commits).
And finally, use binary commits whenever you're recording anything
that's not NL-separated lines.
Juliusz
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
