Printable View
i have a thread in my program that always run as long as the program runs ( runs all the time in loop ).
i operate the Thread by the command AfxBeginThread().
i checked the cpu usage of the thead in the task manager, and i saw that the thread takes 100% cpu usage , is that OK? how can i make the CPU usage lower ? ( i tried to switch the priority parameter of the AFXBeginThread function but it doesn't change the CPU usage).:(
Do you mean that it goes up to 100% briefly while AfxBeginThread() is starting or that it stays permanently at 100% once it's started?
thanks for answering john.
it Stays permanently on 100% once it started.
i even checked it when the thread function content is empty , it still takes 100% CPU Usage,so the problem is not the code inside the thread function it's the thread itself.:confused:
Which version of AfXBeginThread() are you calling? The one that takes a pointer to a function or the one that takes a pointer to a runtime class?
Hold it, I just noticed something....
What do you mean here? That AfxBeginThread() is being called from within a loop or that the loop is running within the thread?Quote:
Originally posted by asaf a
i have a thread in my program that always run as long as the program runs ( runs all the time in loop ).
thanks!
the loop is inside the thread , the AfxBeginThread is being called only once.
i use the one with the function pointer not the Runtime class.
i believe it is wrong for the cpu to behave like that ,is it ?
Yes, of course. But now I don't understand something you said earlier. You said...Quote:
Originally posted by asaf a
i believe it is wrong for the cpu to behave like that ,is it ?
Are you saying that this still happens when the thread function is entirely empty? In other words there is no code running in it at all (not even the loop). As soon as it gets called, it immediately returns? Or does it still enter the loop?Quote:
Originally posted by asaf a
i even checked it when the thread function content is empty , it still takes 100% CPU Usage
you mean, you got a thread looks like this?
int WINAPI ThreadProc( LPVOID lpParam )
{
while ( 1 == 1 )
{
// Some code
}
}
?? If you use something like this: take a timer with uiElapse = 1 or something higher ... it doesn't take the whole cpu usage ...
i didn't make myself clear enough , sorry.
when the thread function is empty i dont have that problem, when i add the "While (TRUE)" loop inside the thread function the cpu jumps to 100% ( even when the while loop is empty of code ).
The 100% CPU usage you see for the thread doesn't mean that the thread uses 100% of the total CPU time, but 100% of the time slices it gets assigned by the task scheduler. It's an obvious value for a thread which runs in a tight loop.
It is normal that the "while( true )" code to take your CPU to 100%. That is not an empty code. Your CPU does make alot or comparisons ( ( true == true ) ? ) and it makes them very fast.
You may try to add some Sleep(500) in your loop. That will give to your CPU some rest (in case you don't want your code can wait sometimes).
thanks mr.speed
, but the empty while loop is only for the example . in my program i have lots and lots of comparisons and lot of work inside the while loop and still i get 100% usage.
Thanks gstercken,
Now i understand it better, i had a felling it doesn't take all CPU usage , since i can work with other MS programs (Word,excel,etc. ) while my program runs.
is there a way to see the cpu usage of the entier computer , so i can see the cpu usage that my program takes ?
It's the tight loop that is causing this problem, not AfxBeginThread(). Any tight loop is bound to soak up processor cycles, even if the loop isn't actually doing anything (in fact, especially if the loop isn't doing anything!) Running it in its own thread won't alter that situationQuote:
Originally posted by asaf a
iwhen the thread function is empty i dont have that problem, when i add the "While (TRUE)" loop inside the thread function the cpu jumps to 100% ( even when the while loop is empty of code ).
as i said before , the tight loop is only for example to check the code with/without the loop . originally , there is alot of work inside the thread.
gstercken ,
if the computer is only showing the time slices it gets assigned by the task scheduler slices , why doesn't he show other programs time slices that run at the same time ? , why only my program time slices ?
Okay, but you also said before that the while loop is running continuously throughout the whole time that your program runs. Unless you provide some means of producing idle time (i.e. relinquishing your grip on the processor from time to time) you will end up having a tight loop, which is why you're seeing the problem that you're seeing. It doesn't matter whether the loop is doing a lot of work or only a little work. If it does a lot of work it will just loop more slowly but it will still be looping continuously.Quote:
Originally posted by asaf a
as i said before , the tight loop is only for example to check the code with/without the loop . originally , there is alot of work inside the thread.