Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!brutus.cs.uiuc.edu!apple!sun-barr!texsun!pollux!smu!merlin From: merlin@smu.uucp (David Hayes) Newsgroups: comp.sys.next Subject: Re: Mach's support on distributed process ? Message-ID: <15948@pollux.UUCP> Date: 26 Sep 89 15:27:25 GMT References: <4927@uhccux.uhcc.hawaii.edu> Sender: news@pollux.UUCP Reply-To: merlin@smu.edu (David Hayes) Organization: Southern Methodist University, CSE Dept. Dallas, TX Lines: 17 In article <4927@uhccux.uhcc.hawaii.edu> ree@uhccux.UUCP (Seung Hee Ree) writes: > But there is a catch. If all the clients request for "egrep" >to the server simultaneously, the server will be bottlenecked. So >there has to be some kind of decision making involved as to whether the >server should do a job for the client or not, depends on the status of >the server. Actually, this is not a problem. Even if some clients were to run the grep themselves, and others request that the server do it for them, you would still have the bottleneck. The bottleneck is the fact that the server must read the file for each grep, whether it is local or run on a client. Disk access is your problem here, not CPU power. David Hayes School of Engineering Southern Methodist University merlin@smu.edu uunet!smu!merlin "Argue for your limitation, and, sure enough, they're yours." - Richard Bach