thanks for your snippet, but David is totally correct in stating the performance consumption of your code. While “waiting” for the dteEnd time to be reached it consumes lots of lots of CPU cycles to check the current time again and again. That’s nearly sort of an infinite loop driving your CPU load nearly up to 100%.

Of course you are able to do other things in between. That’s what you have a multi tasking operating system for.

Unfortunately I do not know of a real VBScript Sleep function consuming no CPU cycles.

Regards, Tom.

Just wana thak you Nipo for this wonderfull snippet!

It´s in use at www.dhstation.com for the chat facility stack sinchro!

Thank you very much.
Mayr Fortuna

It doesn’t hurt your CPU at all to run at or near capacity, even for extended periods of time. (Assuming, of course, that you have proper cooling.) That is, after all, what the hardware is designed to do. What becomes important is what your CPU is doing.

In this case, the CPU is running seemingly menial tasks. It’s not performing complex calculations. In essence it’s simply counting. And since this is a low-priority task it will have little effect on any other processes. If another process requires more CPU power, this will simply step down and hand it over willingly.

All in all, while the CPU usage is a measure of what your CPU is doing, it’s not a very accurate measure of how hard it’s actually working. So even though the CPU usage might indicate that the CPU is under a higher than normal load; In this case, it’s not really under any additional stress.

If you’re not comfortable with those levels, try taking it for a test drive. Set a script to sleep for a minute and then perform some normal tasks. Open your browser and Microsoft Word, play a video, etc. You shouldn’t notice any slower system response while performing these tasks despite the fact that the sleep timer is running.

David

Nilpo

Regards,

AF