Path: utzoo!utgpu!cunews!cognos!alzabo!omx!artech!stevex
From: stevex@artech.UUCP (Steve Tibbett)
Newsgroups: comp.sys.amiga.misc
Subject: Re: Gomf is CPU greedy!
Message-ID: <stevex.3270@artech.UUCP>
Date: 7 Jun 91 21:47:21 GMT
References: <223@taloa.unice.fr>
Organization: Artech Digital Entertainments, Inc.
Lines: 38

In article <223@taloa.unice.fr> beust@taloa.unice.fr (Cedric Beust) writes:
>
>    I wanted to have statistics about the CPU use on my Amiga and was
>very suprised to see that gomf (3.0, so launched via runback) used
>about 12 (twelve!) percent of CPU time, and in READY mode, not
>WAITING. So I decided not to use it any more.
>
>    Anyone can corroborate this amazing figure?

And I bet you used XOPER or some other thing that measures the dispatched 
counter that Exec keeps to figure out how busy the task is.

I finally figured out why VirusX and my other programs are getting such an
apparently high number there:

If a program does a loop like this:
	
	while (TRUE)
		{
		WaitTOF();
		if (This==That)
			{
			Do Stuff;
			};
		};

Then it's going to look like it's taking a very high amount of CPU time, 
because it's getting dispatched 60 times a second - but it's not actually
slowing the machine down that much, or using much CPU time at all (near
zero).  

I bet this is what GOMF is doing.  I know it's what my programs are doing,
and I don't see anything wrong with it - Complain to whoever wrote your CPU
time measurer.

--

    ...Steve's Signature (when Steve's at work)...