[comp.sys.amiga.programmer] input.device usage in Xoper

d88-psm@sm.luth.se (Peter Sj|str|m) (04/03/91)

>Is it really at full load, as in cpu usage is 100%?  If so, then input
>device is really using that much time, or xoper is lying.  If the cpu usage
>is NOT 100% then the default display in xoper reports what percentage of
>the usage is used by some task.
  
My Xoper 2.2 says right now:

 CPU:68020/68881     CPU activity: 100.0%	(25 MHz A3000; Xoper is old!)


 07ce9258 Process   Running     0   0.9% --- Xoper                 
 07c08b22 Task      Waiting    20  45.7% --- input.device          
 07c0a428 Task      Waiting    11   0.0% --- scsi.device           
 07c0a7c0 Task      Waiting    12   0.0% --- SCSI bus handler      
 07c0d992 Task      Waiting     5   0.0% --- console.device        
 07c0f1b4 Task      Waiting     5   0.9% --- trackdisk.device      
 07c104e8 Process   Waiting    10   0.4% --- WB_2.x                
 07c16278 Process   Waiting    10   0.4% --- DF0                   
 07c189b0 Process   Waiting    10   0.9% --- Work                  
 07c1e700 Process   Waiting     0   0.0% --- ramlib                
 07c1fff8 Process   Waiting     2   0.4%   1 [ com:dnet/bin/dnet ] 
 07c23c18 Process   Waiting    10   0.0% --- RAM                   
 07c29c18 Process   Waiting     0   0.0%   3 [ iprefs ]            
 07c451f0 Process   Waiting     0   0.0%   8 [ fterm ]             
 07c58fb8 Process   Waiting     4   0.0%   0 RexxMaster            
 07c5f090 Process   Waiting    21   0.0%   4 [ c2/autocli ]        
 07c63180 Process   Waiting     1   2.3%   2 [ Workbench ]         
 07c6de60 Process   Waiting     0   0.0% --- Blanker               
 07c74fe8 Process   Waiting    21   0.0% --- DoubleClick           
 07c76778 Process   Waiting     0   0.0%   0 SYS:System/CLI        
 07c78aa8 Process   Waiting     0   0.0%   0 SYS:System/CLI        
 07c79ba0 Process   Waiting     5   0.0% --- CON                   
 07c94e60 Process   Waiting     0   2.3% --- MemClock              
 07c96350 Process   Waiting     5   0.0% --- CON                   
 07cb26d8 Process   Waiting     2   0.0% --- MyMenu                
 07cb93d0 Process   Waiting     0   0.0%   5 Background CLI        
 07cbaa20 Process   Waiting     0   0.0%   6 Background CLI        
 07cbe3e0 Process   Waiting     5   0.0% --- NULL                  
 07cdc7b0 Process   Waiting   -20   0.0% --- RebootWbMenu          
 07cde7f0 Process   Waiting     0   0.0%   9 [ fterm ]             
 07ce0630 Process   Waiting     0   0.0% --- SID                   
 07cea348 Process   Waiting     0   0.0%   7 [ sys:c2/snap ]       
 07cfc8e8 Process   Waiting     5   0.0% --- PopUpMenu             
 07d044f8 Process   Ready       0  45.3% --- MandFXPV3             
 07d2caf0 Process   Waiting     5   0.0% --- CON

	As you can see when I leave the computer for a few seconds running
MandFXP input.device take 47 percent. And I am not moving the mouse or
anything! Is input.device taking half my 68030 power????

	/Peter

                              ---===***===---
Peter Sjostrom	 INTERNET:  d88-psm@sm.luth.se	      PHONE:  +46 920 67653
Aurorum 4:13	     UUCP:  {uunet,mcvax}!sunic.se!sigma.sm.luth.se!d88-psm
S-951 65 Lulea		Everytime a change is made, the world seems to fall
Sweden			apart ... like when my world fell apart - Alf
			      ---===***===---

jesup@cbmvax.commodore.com (Randell Jesup) (04/04/91)

In article <9104031312.AAtau07511@tau.sm.luth.se> d88-psm@sm.luth.se writes:
>My Xoper 2.2 says right now:
>
> CPU:68020/68881     CPU activity: 100.0%	(25 MHz A3000; Xoper is old!)
>
> 07ce9258 Process   Running     0   0.9% --- Xoper                 
> 07c08b22 Task      Waiting    20  45.7% --- input.device          

> 07d044f8 Process   Ready       0  45.3% --- MandFXPV3             
>
>	As you can see when I leave the computer for a few seconds running
>MandFXP input.device take 47 percent. And I am not moving the mouse or
>anything! Is input.device taking half my 68030 power????

	Note that intuition runs on input.device.  I suspect Xoper is being
fooled by the fact that you were doing something with intuition in order to
tell Xoper to save those results away.  The proper way to measure that would
be to have xoper measure usage starting after the selection (and perhaps have
a delay before starting to allow the system to go back to normal.)

	It also may well be an artifact of how XOper measures this, though
it's impossible to test.  A better test: do a dhrystone without touching
the mouse.  Now do a dhrystone while waving the mouse around as much as 
possible.  The difference may be measurable, but will by no means be ~50%.
You could also disable around the dhrystone, to see the total difference
all other tasks and all interrupts make.  Note that vblank is an appreciable
amount of this amount, and any commodities can have a large affect on the
amount time used by input.device!

-- 
Randell Jesup, Keeper of AmigaDos, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com  BIX: rjesup  
Disclaimer: Nothing I say is anything other than my personal opinion.
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")  ;-)