Sleep() causing unexplained reduction in cpu load

[sajanphilip]

I have written a test code using timer delegates. About 30 methods are delegated and will be called on the expiry of a timer. This causes the cpu load to spike up every 2 seconds. While trying to optimize this code, i added a "sleep(29)" just before delegating it. The result shouldn't be any different as the timeout gets shifted by 29ms for all the timeouts. But this has cut down the cpu load by 50%. I am quite happy with the result but couldn't find any logical explanation for the reduction in cpu load.Can someone please explain why this is happening?

Thanx in advance...

[Mario F.]

But this has cut down the cpu load by 50%. I am quite happy with the result but couldn't find any logical explanation for the reduction in cpu load.Can someone please explain why this is happening?

If I'm not mistaken it happens because the timer is taxing the cpu. The sleep simply puts the thread... well, to sleep. When the timer resumes, it sees it needs to fire and does its thing.

[Wraithan]

Your CPU load maybe 100% but I bet you if you ran another application while you were doing that, it would run decently. When you tell a thread to go to sleep, and specify a short sleep duration, and the processor has nothing better to do, it will wake up the thread and tell it to get back to work. But if the CPU has something better ( or equally as good) to do, then sometimes the sleep will be longer than the specified time because sleep basically means "Hey, I got nothing to do for at least #, let someone else have a turn"

[sajanphilip]

Thanx guys. I was trying out the same thing using a simple code. Executing it each time took different amounts of time.

[matsp]

Also bear in mind that if you spread a load (e.g. adding sleeps), it will perhaps use the same amount of CPU time overall [if not more], but it will be over a longer timeframe. This only matters if there is other work to be done. Using 100% CPU is not a problem if it happens only some of the time - it's only a problem if the CPU is loaded to 100% for extended periods.

--
Mats