[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Import performance with David Kimdon's full-text patch vs vdelta

From: Brandon Ehle <azverkan_at_yahoo.com>
Date: 2004-01-05 18:57:17 CET

>>That you got a similar error for perforce lends credence to the
>>hypothesis that you are reporting a bug in your testing procedure
>>rather than the tools being tested.
> Ease up there Tom. My understanding of what Brandon said is that he ran
> into a limitation of his *shell*, not of arch or perforce.

Yes, the bug lies in my shell.

>> > I've omitted the Perforce and Arch times for the Mozilla
>> > import because I could not do these operations in a single
>> > (recursive) call like SVN and CVS (even though I could get
>> > these times via xargs).
> My understanding of what Brandon said here (and *please* correct me if
> I'm wrong) is that Subversion allows you to recursively import a whole
> directory tree in one command like this:
> $ svn import foodir
> but that Arch and Perforce do not have recursive imports so you have to
> do something like (again, I'm guessing here):
> $ arch import foodir/file1 foodir/file2 foodir/dir1 ...
> So if Brandon used some mechanism (UNIX find, perhaps) to generate all
> the filenames in the Mozilla tree and pass them to arch via ARGV, that
> he exceeded the limit of ARGC--a limitation of his shell.

This is exactly the case (only my command is "tla add"). Because I have
to do the import in multiple calls for Perforce and Arch, I decided not
to post the results of this test (even though I did obtain such results
via "find | xargs tla add" or "find | xargs p4 add") as CVS / SVN
could have an unfair advantage unless I recompile my shell with a bigger

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jan 5 18:57:57 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.