Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!bcm!dimacs.rutgers.edu!aramis.rutgers.edu!paul.rutgers.edu!njin!uupsi!sunic!dkuug!diku!thomas
From: thomas@diku.dk (Thomas Nikolajsen)
Newsgroups: comp.sys.amiga.misc
Subject: Re: Gomf is CPU greedy!
Message-ID: <1991Jun21.105928.20059@odin.diku.dk>
Date: 21 Jun 91 10:59:28 GMT
References: <223@taloa.unice.fr> <stevex.3270@artech.UUCP> <240@taloa.unice.fr> <stevex.3288@artech.UUCP>
Sender: thomas@rimfaxe.diku.dk
Organization: Department of Computer Science, U of Copenhagen
Lines: 21

stevex@artech.UUCP (Steve Tibbett) writes:

>>      Right. I didn't use Xoper but since then I've seen the figures vary
>>      considerably from one measurer to the other. And anyway, there is
>>      no ultimate way to measure the CPU time on the Amiga :-(

>Sure there is - start an interrupt and sample the ExecBase->ThisTask.  I wonder
>what ThisTask points to when no task is currently "Running"?

Not a good idea, where did you se that method documented?
Try using tc_Switch and tc_Launch (all tasks), whats between is idle time,
same method to measure time used by tasks.

>>      I'll keep GOMF3 in a drawer and will take it out when necessary.

I tried the above, and GOMF (version 2.xx) is not that CPU hungry (circa 5%).

>    ...Steve's Signature (when Steve's at work)...
I tried to reach Steve with email, but it bounced at artech (stevex unknown).

thomas