Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!pasteur!cory.Berkeley.EDU!navas
From: navas@cory.Berkeley.EDU (David C. Navas)
Newsgroups: comp.sys.amiga.programmer
Subject: Re:  Amiga system usage statistics (AmigaDOS 1.3)
Message-ID: <12388@pasteur.Berkeley.EDU>
Date: 2 Apr 91 17:16:58 GMT
References: <ben.5464@epmooch.UUCP> <1991Mar25.161731.29334@odin.diku.dk> <ben.5484@epmooch.UUCP>
Sender: news@pasteur.Berkeley.EDU
Reply-To: navas@cory.Berkeley.EDU
Lines: 16

In article <ben.5484@epmooch.UUCP> ben@epmooch.UUCP (Rev. Ben A. Mesander) writes:
>I've noticed that the amount of CPU usage by input.device varies from almost
>nothing to 40% of the CPU with things such as screen resolution. I'm not
>sure everything input.device does, but perhaps some non-obvious things are
>being accounted to it. I'm not sure what...

If I recall correctly, intuition does a lot of its stuff "under"
input.device's task.  Personally, I'd stick an input handler with a very *large*
priority, and suck up all the input stream before intuition wakes up.  Although
I don't know if she'd like that very much :)

Disclaimer:  ain't never written an input handler in my life.  Figure it out...

David Navas                                   navas@cory.berkeley.edu
	2.0 :: "You can't have your cake and eat it too."
Also try c186br@holden, c260-ay@ara and c184-ap@torus