Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!viusys!uxui!unislc!dave
From: dave@unislc.uucp (Dave Martin)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Amiga system usage statistics (AmigaDOS 1.3)
Message-ID: <1991Apr1.202931.12756@unislc.uucp>
Date: 1 Apr 91 20:29:31 GMT
References: <1991Mar25.161731.29334@odin.diku.dk>
Organization: unisys
Lines: 35

From article <1991Mar25.161731.29334@odin.diku.dk>, by bombadil@diku.dk (Kristian Nielsen):
> 
> BTW, I suspect that Xoper isn't that accurate in its timings... On my GVP
> 28Mhz 3001 it likes to report that input.device is using about 40% of
> CPU-time at full load (ray-tracing or similar). I really don't hope that
> this is the case! (and if it is, how is a stock A500/2000 to run at all??)
> Any comments on this?

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.

Example

CPU USAGE 12%

input.device 40%

Of the 12% cpu usage, input.device accounts for 40% of that.

You can get xoper to report the actual cpu usage instead of the relative
cpu usage for tasks by typing USAGE.

P.S.  Has anyone had troubles getting xoper to work correctly with its
startup script capability?  I can't get xoper to live on the workbench
screen when I do this, even when I include the commands to explicity place
it on the workbench.  It insists on using a custom screen.  This is with
WB2.02

-- 
VAX Headroom	Speaking for myself only... blah blah blahblah blah...
Internet: DMARTIN@CC.WEBER.EDU                 dave@saltlcy-unisys.army.mil
uucp:     dave@unislc.uucp or use the Path: line.
Now was that civilized?  No, clearly not.  Fun, but in no sense civilized.