Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!nosc!ucsd!ames!haven!purdue!decwrl!labrea!Portia!Jessica!davef
From: davef@Jessica.stanford.edu (David Finkelstein)
Newsgroups: comp.sys.mac
Subject: Re: Slow appleshare using CAP v5.0
Message-ID: <3546@Portia.Stanford.EDU>
Date: 2 Sep 88 16:17:28 GMT
References: <15701@shemp.CS.UCLA.EDU>
Sender: news@Portia.Stanford.EDU
Reply-To: davef@Jessica.stanford.edu (David Finkelstein)
Organization: Stanford University
Lines: 27

In article <15701@shemp.CS.UCLA.EDU> korfhage@CS.UCLA.EDU (Willard Korfhage) writes:
>
>   I just put verions 5.0 of the Columbia Appletalk Package (CAP) on our
>VAX 11/750, and it is extraordinarily slow.  A 2.2 Mbyte file took 23
>minutes to transfer from the vax to the mac via a Kinetics Fastpath 2.  We
>had intended to back up our hard disks over the network, but it would take
>about 10 hours to back up our 40 Mbytes, which is clearly outrageous.

Yup, aufs can be slow.

>
>   Our equipment is a Kinetics Fastpath 2 that is fairly new, a Vax
>   11/750, and Mac IIs. The macs have Appleshare v1.1
>

Are you running Ethertalk or LocalTalk on your Mac IIs?  Believe it or
not, in our testing aufs is almost *twice* as slow on Ethertalk as on
LocalTalk.  It just takes a while to translate the Ethertalk packets
into AppleTalk-in-IP packets.

We just installed a new Fastpath 4 with the K-Star code from Kinetics,
and performance is much better.

-----------------
David Finkelstein
Academic Information Resources
Stanford University
davef@jessica.stanford.edu