Path: utzoo!attcan!uunet!lll-winken!ames!think!kulla!fad From: fad@kulla (Franklin A Davis) Newsgroups: comp.sys.next Subject: Re: Slow when on a network? Message-ID: <30213@news.Think.COM> Date: 27 Sep 89 16:39:22 GMT References: <30018@news.Think.COM> <6255@pt.cs.cmu.edu> Sender: news@Think.COM Reply-To: fad@kulla.UUCP (Franklin A Davis) Organization: Thinking Machines Corporation Lines: 33 In article <6255@pt.cs.cmu.edu> avie@wb1.cs.cmu.edu (Avadis Tevanian) writes: >In article <30018@news.Think.COM> fad@think.com (Franklin A Davis) writes: >>I notice that even under 1.0, BreakApp is really slow and jerky. My >>NeXT is on a network with lots of Suns, Vaxen, and Lisp Machines. A >>few dozen filesystems are nfs mounted on the NeXT. > >You must have some system daemon going wild, perhaps because of something >on your network. I currently have 36 NFS file systems mounted on my machine >and BreakApp has no problem at all. If you know how, you might try running >a "ps" in a Terminal to see if there are any processes eating up cpu >cycles. I think you're right, because I tried it again, and now there's no problem. ps says the tasks (kernel-task) and /NextApps/Shell -MachLaunch 18 124 are the only very busy ones. I'm surprised that they each use about 1/3 of elapsed wall-clock time in cpu time, but I suppose there's a lot of system stuff involved in drawing etc. Thanks for your suggestion. >Also, is it possible that someone is logged in to your machine over the >network? No, no one knows about it yet :-) --Franklin franklin a davis Thinking Machines Corp. Cambridge, MA 02142 617-876-1111{ames, harvard, mit-eddie, uunet}!think!fad Let the four winds blow you safely home!