Return to BSD News archive
Xref: sserve comp.windows.x.i386unix:1517 comp.os.386bsd.questions:2382 Newsgroups: comp.windows.x.i386unix,comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!crcnis1.unl.edu!wupost!howland.reston.ans.net!usc!cs.utexas.edu!utnut!torn!nott!bnrgate!bnr.co.uk!zaphod.axion.bt.co.uk!uknet!cf-cm!paul From: paul@isl.cf.ac.uk (Paul) Subject: Re: XFree1-2 + 386BSD performance Message-ID: <1993May12.182849.29379@cm.cf.ac.uk> Sender: news@cm.cf.ac.uk (Network News System) Organization: /usr/local/lib/rn/organisation References: <1993May12.025731.29769@latcs1.lat.oz.au> <1993May12.144311.14744@sifon.cc.mcgill.ca> Date: Wed, 12 May 1993 18:28:47 +0000 Lines: 34 In article <1993May12.144311.14744@sifon.cc.mcgill.ca> storm@cs.mcgill.ca (Marc Wandschneider) writes: >In article <1993May12.025731.29769@latcs1.lat.oz.au> wongm@ipc5.lat.oz.au (M.C. Wong) writes: >>Hi, >> I have a question about the performanc of running XFree1.2 on >>386BSD 0.1. In multi-user mode running 3 xterms, xeyes, xclock, >>xload and xbiff, when I do serious compiling in one of the window, >>I realize that the performance of the overall X activities are >>intolerable slow and it chokes very very much, and I can hardly >>see my mouse moving/appearing on the screen for 5-10 seconds. > > This is rather bizarre---I ran XFree86 and 0.1 on my 486/50; and > with Xeyes, Xclock, and three compiles running, the load average > hit about 2.27, but the machine was still quite responsive, and > the mouse and windows still moved around as fast as they had > before I started all the builds. I wish I was so lucky. When doing compiles that access disk a lot my system hangs until the disk activity stops. I think what's happening is that disk interrupts are crowding out everything else. Is there some way of preventing this, it would make it a lot easier to run background compiles. At the moment it's like running a single tasking system because when the disk is being accessed nothing else happens. Incidentally, my drive is an IDE, I get the feeling that this doesn't happen with SCSI which is why not everyone sees it. -- Paul Richards, University of Wales, College Cardiff Internet: paul@isl.cf.ac.uk