Posted by Hans Salvisberg on 2007-01-09 08:47 CET
(In reply to: High CPU consumption posted by Aegidius on 2007-01-08 13:54 CET)

Hi Aegidius, With CP::yield() you will always give up your time slice immediately, and any other thread waiting to run will be able to proceed. This means that even though your test program is sucking up all *idle* time, any other concurrent applications will get as much CPU time as they want. I would expect CPTimer::delay(10) to behave even better, but try CPTimer::delay(100) -- that should definitely make your Champ application go idle, without causing any noticeable loss of responsiveness. Try Process Explorer from www.sysinternals.com and enable the CPU History column to see what is running and how much CPU time it's getting/taking. Let me know what you find... Hans