Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!reed.UUCP!mdr
From: mdr@REED.UUCP (Mike Rutenberg)
Newsgroups: mod.protocols.appletalk
Subject: Serious AppleTalking
Message-ID: <8603090139.AA07903@reed.UUCP>
Date: Sat, 8-Mar-86 20:39:30 EST
Article-I.D.: reed.8603090139.AA07903
Posted: Sat Mar  8 20:39:30 1986
Date-Received: Tue, 11-Mar-86 01:20:54 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 20
Approved: info-applebus@c.cs.cmu.edu

I want to know how people find Appletalk when used as a general purpose
LAN under a serious load.  I might suspect all is fine, but would love
to hear somebody with actual experience say so.

Are you running file servers?  Do you have 20 Macs on 1 Appletalk
talking IP?  Do you have a large network with Ethernet/Appletalk
gateways?  What do you think?

What I would really love is a full blown operational report on Appletalk,
but more specifically:
  - How does the network stand up under a reasonable load?
  - If I have 20 Macs on one Appletalk logging into a Vax
    through an Ethernet/Appletalk gateway, will perceived performance
    be decent (eg. x kbps)? (assume Vax speed isn't an issue)

I would guess Apple has lots of practical experience, but Stanford, CMU
and others also seem to be doing Internetworking work with Appletalk.
Any of these groups (& others) are encouraged to reply.

Mike Rutenberg