[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: time for LDM to transfer a 200Mb file (fwd)

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: time for LDM to transfer a 200Mb file (fwd)
  • Date: Wed, 6 Sep 2000 19:02:35 -0600 (MDT)

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================

---------- Forwarded message ----------
Date: Wed, 6 Sep 2000 18:04:10 -0600
From: Mike Schmidt <address@hidden>
To: address@hidden, address@hidden
     address@hidden
Subject: Re: time for LDM to transfer a 200Mb file

Russ,

I did a long needed reboot on zero to roll-in 40+ patches.  Times look
better, although the system is now very lightly loaded;

# time cp /ldmtest/newpq-32/bigprod.raw /scratch/mschmidt

real    0m35.47s
user    0m0.01s
sys     0m3.26s

Let's try this again tomorrow when the system is back to steady-state.

mike

On Sep 6,  5:23pm, Russ Rew wrote:
> Subject: time for LDM to transfer a 200Mb file
> Mike,
>
> I reported earlier the difference between using "cp" (from a local to
> an NFS-mounted file system) versus using "ftp" to transfer a single
> 200 Mbyte file from buddy to zero:
>
>   cp  122 sec
>   ftp  41 sec
>
> Just for completeness, I timed the LDM doing the same thing:
>
>   ldm  64 sec
> ...