OpenEuphoria

Re: Timeing Question

• Posted by Kat <gertie at PELL.NET> Feb 08, 2001
• 459 views

On 8 Feb 2001, at 11:00, Euman wrote:

> 
> 
> > There are 65,536 ticks in one hour until you use tick_rate(100), then you
> > have 360,000 ticks in one hour.
> >
> > I tried this:
> >
> >     include machine.e
> >     atom t
> >
> >     t = time()
> >     while time() = t do  -- wait next tick
> >     end while
> >     ? 1/(time()-t)
> >
> >     tick_rate(100)
> >
> >     t = time()
> >     while time() = t do
> >     end while
> >     ? 1/(time()-t)
> >
> > For some reason I don't ever get 18.2 ticks per second in the first
> > instance; I get either 16.66 or 20.  In the second instance I always get a
> > result close to 100.
> >
> > -  Colin Taylor
> >
> > Euman wrote:
> >
> > If There are 64K (65,536) ticks in one hour
> >
> > Why is it I cant seem to get this to work
> > 18.204 ticks per second
> >
> >
> >
> 
> This would explain the difference in timeing of loops
> (profiling)
> 
> If you run a program to test for speed
> occasionally the times are different for the same algorytm.
> 
> Maybe Robert hasnt been told about this either.
> or maybe he knows but hasnt done anything to correct it.

The OS determines how many ticks to use on each program. If one app has a higher
priority than your's, it will get available ticks before your app will. And it
may interrupt
your program to do OS stuff, like swap disc space.

Kat