Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ames!apple!apple.com!desnoyer From: desnoyer@apple.com (Peter Desnoyers) Newsgroups: comp.protocols.appletalk Subject: Re: Re- LocalTalk Speeds Message-ID: <4474@internal.Apple.COM> Date: 29 Sep 89 19:39:27 GMT References:Sender: usenet@Apple.COM Organization: Apple Computer, Inc. Lines: 17 One tack you might try to reduce network load in a Mac lab - Instead of using an environment such as MPW where you load the compiler every time you do a compile, look for an integrated programming environment that loads the compiler into memory along with the editor and everything else. (like the Turbo C integrated environment on the PC) That way you only do one big net transaction when a student starts working, instead of once for every recompile. I don't know if such a package exists - I have only used MPW. This can be looked at as a more general tradeoff - is the extra memory to keep everything the student needs running under Multifinder cheaper than the network and server capacity needed with less memory? Peter Desnoyers Apple ATG (408) 974-4469