Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!rex!uflorida!mephisto!mcnc!thorin!unc!cullip
From: cullip@unc.cs.unc.edu (Timothy Cullip)
Newsgroups: comp.sys.amiga.tech
Subject: Xoper and input.device
Message-ID: <11547@thorin.cs.unc.edu>
Date: 20 Jan 90 14:01:56 GMT
Sender: news@thorin.cs.unc.edu
Lines: 15

I just got Xoper off the network and was running it while I had my
ray tracer running in the background.  Nothing else was currently
running (other than normal operating system stuff like devices).  
Xoper reported that my raytracer only got about 40% of the
cpu use (cpu activity 100%) while input.device was sucking up about
40% also even though I wasn't doing any inputing.  

My question is why is input.device such a cpu hog?  Can anything be
done to give more time to a cpu intensive program like my raytracer?
Bumping up its priority doesn't seem to help much, I don't want its
priority high with respect to other CLI tasks, I would just like 
input.device to not use so much cpu time.  Just what is input.device
doing other than handling the keyboard and mouse?

   Tim Cullip