In a message dated 10/26/2010 11:58:58 AM Pacific Daylight Time, 
[email protected] writes:


> In testing, it's the INPUTIF statement that's utilizing the CPU, not the
> timer calculation.
> 
> Is there a better, less CPU intensive way to do this? 
> 
> Thanks in advance. >>
> 


INPUTIF checks the type-ahead buffer every time slice.  You're getting so 
many slices that your CPU is consumed with this one task of checking the 
type-ahead buffer.  It's frenetic, a CPU on crystal meth.

In the old days, we would say Release Timeslices RQM.  Today you can solve 
that issue as well, by adding a Sleep for a 1 second.  On systems that allow 
sleeping for periods less than a second, you only really need to add a 
sleep for a tenth of a second, to see your CPU suddenly quiesce.

Will Johnson
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users

Reply via email to