Return to BSD News archive
Xref: sserve comp.windows.x.i386unix:1523 comp.os.386bsd.questions:2386
Newsgroups: comp.windows.x.i386unix,comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!uunet!utcsri!newsflash.concordia.ca!sifon!storm
From: storm@cs.mcgill.ca (Marc Wandschneider)
Subject: Re: XFree1-2 + 386BSD performance
Message-ID: <1993May12.202203.27917@sifon.cc.mcgill.ca>
Sender: news@sifon.cc.mcgill.ca
Organization: SOCS - Mcgill University, Montreal, Canada
References: <1993May12.025731.29769@latcs1.lat.oz.au> <1993May12.144311.14744@sifon.cc.mcgill.ca> <1993May12.182849.29379@cm.cf.ac.uk>
Date: Wed, 12 May 1993 20:22:03 GMT
Lines: 26
In article <1993May12.182849.29379@cm.cf.ac.uk> paul@isl.cf.ac.uk (Paul) writes:
>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.
Hrm. I was running a no-name 486/50DX with a 12ms Maxtor IDE
drive, and a 14ms Quantum SCSI disk. Most of the builds were
running on the IDE drive.
However, it might be worth pointing out that I was running X386mono,
since the 8514 isn't quite supported yet....
Toodlepip!
Marc 'em.
--
----------------------------------------------------------------------------
storm@cs.mcgill.ca SOCS Staff, McGill University
Marc Wandschneider (514)398-5924
386bsd--ftp agate.berkeley.edu:/pub/386BSD/386bsd-0.1, mail for FAQ info