On Tue, Jul 09, 2002 at 09:25:03AM -0700, Jim Benson wrote:
> Have you read the thread at:
> 
> http://lists.squeakfoundation.org/pipermail/squeak-dev/2002-May/014121.html

Now I have.  Ugh.  Thanks for the link.
 
> I don't remember how the symptoms you described have been addressed in the
> latest release.

>From what I see from that thread and this one, the difference is that he was
running UML while I am running native so there shouldn't be as much of a
penality .. so it must be something that is doing within that loop, as with
more gettimeofday calls, significantly more load.   On a completely unrolled
test, its churning out 200K gettimeofdays in 0.080s 

So to my (squeak untrained) eyes squeak it is still eating far too many
cycles when it should be idle.  And I dont see any syscall or glibc calls
being done.  Could someone briefly explain or point me where to look on
why's this polling needed?

> I assume that you are using *nix. More than likely the Zurgle stuff isn't
> causing the problem (it does not do anything to cause more idle events that
> I know of).

Yup, this is linux.  Maybe it was the uptime, since the only real difference
was that it had been running for far more time.

> ----- Original Message -----
> From: "Ragnar Hojland Espinosa" <ragnar at linalco.com>
> To: <squeak-dev at lists.squeakfoundation.org>
> Sent: Tuesday, July 09, 2002 2:30 AM
> Subject: Re: excessive gettimeofday calls (idle cpu usage) in last gamma
> 
> 
> > On Tue, Jul 09, 2002 at 02:22:36AM -0700, Jim Benson wrote:
> > > Ragnar,
> > >
> > > Which version of Zurgle, and which version of Squeak?
> >
> > Last of both, Zurgle10b and gamma #4913
> >
> > > ----- Original Message -----
> > > From: "Ragnar Hojland Espinosa" <ragnar at linalco.com>
> > > To: <squeak-dev at lists.squeakfoundation.org>
> > > Sent: Tuesday, July 09, 2002 2:15 AM
> > > Subject: excessive gettimeofday calls (idle cpu usage) in last gamma
> > >
> > >
> > > > Leaving a zurgled squeak running idle overnight, this morning I saw it
> > > > chewing a constant 21.4% of CPU time which is obviously very bad on a
> dual
> > > > 1.2 GHz.   So I stopped it and started a plain squeak, left it idle
> > > > minimized and its still chewing up far too many cycles, at around a
> > > minimum
> > > > 4.5% with periodic ramps to 10% and < 30%.
> > > >
> > > > A breif look over the processes show that the overnight one was doing
> > > 20886
> > > > gettimeofday syscalls per second while the new one is currently doing
> 6503
> > > /
> > > > sec
> > > >
> > > > --
> > > > Ragnar Hojland - Project Manager
> > > > Linalco "Especialistas Linux y en Software Libre"
> > > > Tel: +34-91-5970074 Fax: +34-91-5970083
> > > >
> > >
> > --
> > Ragnar Hojland - Project Manager
> > Linalco "Especialistas Linux y en Software Libre"
> > Tel: +34-91-5970074 Fax: +34-91-5970083
> >
> 
-- 
Ragnar Hojland - Project Manager
Linalco "Especialistas Linux y en Software Libre"
Tel: +34-91-5970074 Fax: +34-91-5970083