On Thu, Mar 4, 2010 at 19:43, Neels J Hofmeyr <neels_at_elego.de> wrote:
> Neels J Hofmeyr wrote:
>> Just a thought: the 'svn up' will copy all those pristines to the user area.
>> If it's faster to copy from the other device than within the same device
>> (where the working copy is), copying everything can be faster.
It really depends. If the source is on a network drive (which I
assumed because it was for a whole development team), then a copy of
the metadata+pristines followed by a local-restore could be faster.
But it was mostly just a thought. I certainly don't recommend making
use of such "internal" knowledge of the capabilities of the .svn
> Plus, the 'svn up' will, probably, *validate the checksums* of all pristines
> while restoring the working copy. That would slow the whole thing down
> substantially. Hmmm...
I really doubt it. My belief is the process will be I/O-bound, so the
extra CPU spent computing checksums will not be a big issue (unless
you have an SSD or some other fast local drive, of course). That was
part of our earlier discussion: assuming an I/O-bound process, rather
than CPU-bound. But given that certain scenarios could end up
CPU-bound, this is why we'd like to optimize-away the checksums
(rather than leaving them always-on, per default).
Received on 2010-03-05 03:04:05 CET