Ulrich Müller wrote:
>> Can you try the associated branch? It just changes the calling code
>> to request all file content in one pass, rather than one file at a
>> time.
>
> This brings the time down from 54 min to 9 min.
>
> But it still accesses the repote repo during export (in fact, from the
> transferred volume I would conclude that everything is re-fetched over
> the network).
>
> Ulrich
>
A lightweight checkout doesn't have any history locally, so it has to. I
suppose one option would be to have export see what files are locally
modified, and use the wt for unchanged files, and fall back to the
repository for the rest. That would complicate the code a fair amount,
though.
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ulrich Müller wrote:
>> Can you try the associated branch? It just changes the calling code
>> to request all file content in one pass, rather than one file at a
>> time.
>
> This brings the time down from 54 min to 9 min.
>
> But it still accesses the repote repo during export (in fact, from the
> transferred volume I would conclude that everything is re-fetched over
> the network).
>
> Ulrich
>
A lightweight checkout doesn't have any history locally, so it has to. I
suppose one option would be to have export see what files are locally
modified, and use the wt for unchanged files, and fall back to the
repository for the rest. That would complicate the code a fair amount,
though.
John
=:->
-----BEGIN PGP SIGNATURE----- enigmail. mozdev. org/
n88cACgkQJdeBCY SNAANJQgCghjqxu 4ubt6P8ziTRFkSq GHbT I/pFHjeh39w+ fhOzN
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAks
OkIAn0MWBayWi4v
=NFCC
-----END PGP SIGNATURE-----