On Sep 13, 2005, at 17:11, Paul Koning wrote:
>> Got any large files? I noticed an apparent several-minutes
>> pause while loading a dump of our repository, but it turns out
>> it was just uploading a 300-MB file.
> That doesn't explain the 2 minute stall at the end of the process; the
> last file is a small .h file.
> But yes, there are some big files. The biggest is 38 MB, and there
> are 194 files bigger than 1 MB. They are all binary files of various
> kinds, naturally.
Well, wait, you were talking about two different things. You noted
that, during the cvs2svn conversion, you saw a long delay at a
On Sep 13, 2005, at 15:54, Paul Koning wrote:
> Oh yes, one more data point. In one of my test runs of cvs2svn, I
> watched the log entries scroll by. In phase 5, where the SVN commits
> are done that create the equivalent of the CVS history, one of the
> commits took a very long time (many minutes), long enough that I
> thought it had gotten wedged due to a bug before I finally let it run
> to completion and noticed all was well.
I responded to this, saying it might be a single large file being
committed at that point, and I still think that's a likely answer.
Not sure if many minutes is a reasonable time for a commit of a 38MB
file to take... suppose I could try it. But since that's only an
issue at the time where you add such a large file to the repository,
I'm hoping it's not something you'll run into every day, and so the
fact that it takes some time should not be a hindrance to you.
The other issue you talked about is that, at the end of a checkout,
it waits for a long time:
On Sep 12, 2005, at 21:21, Paul Koning wrote:
> The first test is to checkout a full working directory, on a rather
> large repository (35,000 revisions, and the CVS working directory is
> foo MB).
> The other puzzle is that svn sits for a minute or two at the end,
> without producing any output and without any significant activity that
> I can see. [snip]
I don't think that's related to the cvs2svn conversion issue; I don't
think it has anything to do with how many files you're getting or how
big they are. Indeed, I have no idea what causes it; we see this
phenomenon often (but not always) on our company's Subversion
repository, and it's driving my coworkers nuts. Actually I'm not sure
if it's exactly the same as what you're seeing, because we see it
mostly when committing, after the file data has been sent, but before
it returns control to the prompt. And we also see it when updating a
working copy, after all the data has been received but again before
regaining command control. But I don't know what to do about it,
which is why I didn't respond to that part of your question.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Sep 13 20:50:01 2005