Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!ub!dsinc!bagate!cbmvax!jesup From: jesup@cbmvax.commodore.com (Randell Jesup) Newsgroups: comp.sys.amiga.programmer Subject: Re: Amiga system usage statistics (AmigaDOS 1.3) Message-ID: <20153@cbmvax.commodore.com> Date: 27 Mar 91 05:36:57 GMT References: <1991Mar25.161731.29334@odin.diku.dk> <1991Mar26.033402.2720@research.canon.oz.au> Reply-To: jesup@cbmvax.commodore.com (Randell Jesup) Organization: Commodore, West Chester, PA Lines: 15 In article <1991Mar26.033402.2720@research.canon.oz.au> andy@research.canon.oz.au (Andy Newman) writes: >On my A1000 Xoper reports that input.device is consuming around 15% of the >total CPU when no user input events are occuring (keyboard or mouse) and around >30% when I bang on the keyboard or move the mouse. Anyone have an explanation? >Is input.device using timers to wake itself up every now and then? Yes: Intuiticks, etc. They pass through the entire chain. 15% seems a bit high, though. Screen blankers, hotkeys, etc may be the reason. -- Randell Jesup, Keeper of AmigaDos, Commodore Engineering. {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com BIX: rjesup Thus spake the Master Ninjei: "To program a million-line operating system is easy, to change a man's temperament is more difficult." (From "The Zen of Programming") ;-)