Re: NFS performance

Doing a data transfer "does not" cause a CPU to be
bound.

A very narrow data path with limited memory causes
the process to be slow but the processor is doing
VERY little work.

The data path is the restriction. Doing massive copying
on a network of twisted pair is both slow and silly.

Most any tape drive made in the last 10 years is
much faster than a "network transfer".

Your comments on the speed of older machines shows a
real lack of experience in these computers.





Lukas Beeler wrote:

On Fri, Aug 14, 2009 at 16:20, Pat Barber<mboceanside@xxxxxxx> wrote:

Where do you get your information from ?

From my job. A few years back (2005, 2006), i usually migrated 2-3

170/270 a month to 520ies.

And it was always awfully slow if you had to use the network route -
not that tapes were any faster, they were just easier to deal with.

Exactly what does "run out of CPU when doing large transfers" mean ?

It means the data transfer process is CPU bound.

How many of those processors have you actually worked on ?

Only the smaller ones. I rarely deal with big machines.

Do you mean that a 170 just quit because it was doing a "large"
data transfer ?

They don't quit, they're just very slow.