Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!mailrus!husc6!bloom-beacon!athena.mit.edu!tada
From: tada@athena.mit.edu (Michael Zehr)
Newsgroups: comp.os.vms
Subject: TK-50 on uVAX 2000
Message-ID: <4687@bloom-beacon.MIT.EDU>
Date: 17 Apr 88 16:29:22 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Reply-To: tada@athena.mit.edu (Michael Zehr)
Organization: Massachusetts Institute of Technology
Lines: 25
Summary: want explaination of slowness


I had a horrible experience the other day for which I have no
explaination.  I was working on a uVAX 2000 with a TK-50 and two
RD-53s (two expansion boxes).  I did an image backup of the system
disk, and it took over 4 1/2 HOURS to finish!!!! I've never seen an
image of an RD53 take longer than an hour before.  Anyone have any
idea why this might me?

(My theories are:

a) disk was *horribly* fragmented (probably not, cuz it was the system
disk and most of those files are put there and then left alone)

b) the uVAX 2K doesn't have a tape and disk controller on the bus (cuz
it has not bus) so the CPU has to do gobs more work than usual, and
that slowed things down by a factor of 4.  (maybe.  i can try it again
/nocrc, which should free up the CPU somewhat.  but an image on a
similar machine the day before didn't take nearly that long...)

)

thanks for any help.

-------
michael j zehr
"My opinions are my own ... as is my spelling."