From: Robert Klemme <shortcutter@...>
Date: 2008-11-10T22:13:20+09:00
Subject: Re: Moving large amount of files, 1.750.000+

2008/11/10 Sebastian Newstream <abeansits@gmail.com>:
> Robert Klemme wrote:
>> On 09.11.2008 18:04, Sebastian Newstream wrote:
> The target system I will use is a virtual Windows 2003 server with a
> mounted network drive. Unfortunatly I have no access to any of the
> hardware.
> But I know there is at least a 100Mbit Ethernet connection between the
> server and the mounted disk.
>
>>
>> Here's the tar variant, since you copy images I assume data is
>> compressed and does not need compression (on your favorite Unix shell
>> prompt):
>>
>> $> ( cd "$source" && tar cf - . ) | ( ssh user@target "cd '$target' &&
>> tar xf - )
>
> Thanks for your tips, but it's a Windows system.

The command above works on a cygwin shell. Alternatively you can use
XCOPY or directly use the Windows Shell (Explorer).

>> If you can physically move the source disk to the target host and then
>> do a local copy with cp -a that's probably the fastest you can go -
>> unless the physical takes ages (e.g. to the moon or other remote
>> locations).
>
> Since our company outsourced the hardware maintenance the moon or across
> the street makes no difference. =(

:-)

> What I meant to ask was, I what way can I change my source code to be
> more effective?

And the answer is and was: don't bother too much because your transfer
is IO bound regardless of programming language or tool used.

Cheers

robert


-- 
remember.guy do |as, often| as.you_can - without end