Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!think.com!mintaka!bloom-beacon!eru!hagbard!sunic!dkuug!iesd!iesd.auc.dk!stig From: stig@iesd.auc.dk (Stig Efsen) Newsgroups: comp.windows.x Subject: Re: OpenWindows 2.0 runs slow on Sun3 50/60(?) Message-ID: Date: 9 Nov 90 12:48:48 GMT References: <9011090400.AA22028@mentor.cc.purdue.edu> Sender: news@iesd.auc.dk (UseNet News) Organization: Mathematics and Computer Science, University of Aalborg Lines: 53 In-reply-to: zhengt@MENTOR.CC.PURDUE.EDU's message of 9 Nov 90 04:00:39 GMT In article <9011090400.AA22028@mentor.cc.purdue.edu> zhengt@MENTOR.CC.PURDUE.EDU (Tong Zheng) writes: Path: iesd!dkuug!sunic!uupsi!rpi!zaphod.mps.ohio-state.edu!swrinde!ucsd!ucbvax!MENTOR.CC.PURDUE.EDU!zhengt From: zhengt@MENTOR.CC.PURDUE.EDU (Tong Zheng) Newsgroups: comp.windows.x Date: 9 Nov 90 04:00:39 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 38 > I have been running OpenWindows2.0 on our Sun3 50/60s > for couple of weeks, and am impressed by the > method of the interface and its DeskSet applications. > But I found that it ran quite slow on the Sun3 50/60s > I am using. There are around 8Mbytes memory on our > Sun3 50/60, and I belive the OpenWindows runs via NSF. > It runs so slow on Sun3/50 that I can hardly work on > multiwindows on my display. It's much better on the > Sun3/60, but still doesn't work fast enough against > the speed of my old&good MIT's simple Wm+Xapplications > interface. ... Stuff deleted ... > Does anyone out there also have this problem? > If anyone has the similar story or any kind of explaination, > ideas or suggestion, I would like to hear about it. > You can either post on the net or send me via e-mail. > > Any information is appreciated. We have been abel to run the OpenWindows 2.0 for about 2 weeks, and I must say that I'm impressed with the graphical layout, especially the pushpin. HOWEVER, the OW 2.0 is the only windows system that I know of, that slows down the computing speed of a 12.5 MIPS SparcStation (which we are currently running on), to the equivalent of a COMMODORE-64. The problem with OW 2.0 is mainly the memory consumption, it wont run, without a lot of disk swapping, on a machine with only 8 Mb of memory. In most cases, 12 Mb isn't really enough, you would have to have 16 Mb. -- ------------------------------------------------------------------------------- Stig Efsen | stig@iesd.auc.dk Aalborg University Center, Denmark |{uunet}...!mcvax!dkuug!iesd.auc.dk!stig Department Of Computer Science | ------------------------------------------------------------------------------- I know that you belive you understand what you think I said, but I am sure you realize that what you heard is not what I meant. -------------------------------------------------------------------------------